FreeBSD Port: ruby-1.9.1.129_1,1

2009-09-10 Thread Benjamin Allen
I was just curious why the ruby 1.9 port hasn't been pushed up to  
patch set 243. It seems to compile and install with no issues when  
RUBY_PATCHLEVEL=243 is set and file hashes are updated. Let me know if  
anything needs to be done on this port to help move it along.


Kind Regards,

Ben
___
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.2.10 update to php5-5.3

2009-09-10 Thread Sudarikov A Alexey
Hello, Tobias.

Thank you! It is waiting for results! Greetings from Russia! ;-)

On Wed, 9 Sep 2009 23:15:18 +0400
Tobias Lott tl...@gamesnet.de wrote:

 On Wed, 9 Sep 2009 17:05:28 +0400
 Sudarikov A Alexey a.sudari...@hoster.ru wrote:

 Please put PHP 5.3 into ports of FreeBSD!
 
 ___
 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

 There is only a BETA 1 Patch for Suhosin

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


Re: devel/9base v2 upgrade to v4

2009-09-10 Thread Sofian Brabez
Hi Jason

On Wed, Sep 9, 2009 at 6:10 PM, Jason J. Hellenthal jas...@dataix.net wrote:

 Would it be possible to fit in 9base-4 before the ports freeze. I am
 planning on going off air within the next couple of weeks and this is my
 preferred window manager and the provided with 9base-4 read command sure
 would come in handy.

 http://dl.suckless.org/tools/9base-4.tar.gz

 Thanks in advance.

 --

  |-|

  Jason J. Hellenthal
  http://www.DataIX.net/
  jas...@dataix.net
  0x691411AC

  - (2^(N-1))


I prefer wait the port freeze of 14 September to update devel/9base but as you
need it. I attached a unified diff which allow you to compile and install the
new version 9base-4 released the 2009/09/27.

As you could see, It needs lot of changes because lot of new binaries are now
in plan9port distribution. That's why I want to wait the port freeze to
correct handle them.

Regards

-- 
sbz
diff -ruN 9base.orig/Makefile 9base/Makefile
--- 9base.orig/Makefile 2009-09-10 10:10:10.0 +0200
+++ 9base/Makefile  2009-09-10 09:50:03.0 +0200
@@ -6,10 +6,10 @@
 #
 
 PORTNAME=  9base
-DISTVERSION=   b20090309
+DISTVERSION=   b20090927
 CATEGORIES=devel
 MASTER_SITES=  http://dl.suckless.org/tools/
-DISTNAME=  ${PORTNAME}-2
+DISTNAME=  ${PORTNAME}-4
 
 MAINTAINER=sbra...@gmail.com
 COMMENT=   Port of various original plan9 tools
@@ -19,17 +19,44 @@
 MANPREFIX= ${PREFIX}/9
 MAKE_ARGS= PREFIX=${PREFIX}/9 CC=${CC} MANPREFIX=${MANPREFIX}/man \
CFLAGS=${CFLAGS} LDFLAGS=${LDFLAGS}
+
 MAKE_JOB_SAFE= yes
-APPS=  awk basename bc cat cleanname date dc echo grep mk rc sed \
-   seq sleep sort tee test touch tr uniq yacc
-MAN1=  ${APPS:S|$|.1|}
-MAN7=  regexp.7
+
+APPS=  ${AWK} \
+   ${BASENAME} \
+   bc \
+   cal \
+   ${CAT} \
+   cleanname \
+   date \
+   ${DC} \
+   du \
+   ${ECHO_CMD} \
+   ${GREP} \
+   hoc \
+   ${LS} \
+   mk \
+   read \
+   rc \
+   ${SED} \
+   seq \
+   sleep \
+   ${SORT} \
+   tee \
+   test \
+   ${TOUCH} \
+   ${TR} \
+   troff \
+   uniq \
+   yacc
+
+MAN1=  ${APPS:S|LANG=C||:C|.*/||:S|$|.1|}
 
 ONLY_FOR_ARCHS=i386 amd64 sparc64
 ONLY_FOR_ARCHS_REASON= has low-level code unavailable for ${ARCH}
 
 post-patch:
-   @${REINPLACE_CMD} -e 's|PREFIX|${PREFIX}/9|' ${WRKSRC}/rc/plan9ish.c
+   @${REINPLACE_CMD} -e 's|PREFIX|${PREFIX}/9|' ${WRKSRC}/lib9/get9root.c
@${REINPLACE_CMD} -e 
'/OBJTYPE!=/s|!=.*|=${ARCH:S,i386,386,:S,amd64,x86_64,:S,sparc64,sun4u,}|' 
${WRKSRC}/lib9/Makefile
 
 post-install:
diff -ruN 9base.orig/distinfo 9base/distinfo
--- 9base.orig/distinfo 2009-09-10 10:10:10.0 +0200
+++ 9base/distinfo  2009-09-10 01:45:57.0 +0200
@@ -1,3 +1,3 @@
-MD5 (9base-2.tar.gz) = f9d30509996ec178702af20fec986e9d
-SHA256 (9base-2.tar.gz) = 
fc60a3af4a2a21167403c099192842e00e5a6416af6b76512262059a203c3534
-SIZE (9base-2.tar.gz) = 301740
+MD5 (9base-4.tar.gz) = af10410542ea6b6875a71e06fdc12c66
+SHA256 (9base-4.tar.gz) = 
704dde999650ce07486a208683475d8f93e8083041bb57a3dc469e12f43eb1d5
+SIZE (9base-4.tar.gz) = 961809
diff -ruN 9base.orig/pkg-plist 9base/pkg-plist
--- 9base.orig/pkg-plist2009-09-10 10:10:10.0 +0200
+++ 9base/pkg-plist 2009-09-10 09:58:14.0 +0200
@@ -1,13 +1,18 @@
 9/bin/awk
 9/bin/basename
 9/bin/bc
+9/bin/cal
 9/bin/cat
 9/bin/cleanname
 9/bin/date
 9/bin/dc
+9/bin/du
 9/bin/echo
 9/bin/grep
+9/bin/hoc
+9/bin/ls
 9/bin/mk
+9/bin/read
 9/bin/rc
 9/bin/sed
 9/bin/seq
@@ -17,12 +22,208 @@
 9/bin/test
 9/bin/touch
 9/bin/tr
+9/bin/troff
 9/bin/uniq
 9/bin/yacc
 9/etc/rcmain
-...@dirrm 9/man/man7
+9/lib/troff/tmac/tmac.v
+9/lib/troff/tmac/tmac.uni
+9/lib/troff/tmac/tmac.twb
+9/lib/troff/tmac/tmac.srefs
+9/lib/troff/tmac/tmac.spe
+9/lib/troff/tmac/tmac.soft
+9/lib/troff/tmac/tmac.skeep
+9/lib/troff/tmac/tmac.sdisp
+9/lib/troff/tmac/tmac.scover
+9/lib/troff/tmac/tmac.s
+9/lib/troff/tmac/tmac.rscover
+9/lib/troff/tmac/tmac.ptx
+9/lib/troff/tmac/tmac.psychrefs
+9/lib/troff/tmac/tmac.pm
+9/lib/troff/tmac/tmac.pictures
+9/lib/troff/tmac/tmac.org
+9/lib/troff/tmac/tmac.nihongo
+9/lib/troff/tmac/tmac.mcs
+9/lib/troff/tmac/tmac.m
+9/lib/troff/tmac/tmac.jsdisp
+9/lib/troff/tmac/tmac.html
+9/lib/troff/tmac/tmac.e
+9/lib/troff/tmac/tmac.cs
+9/lib/troff/tmac/tmac.bits
+9/lib/troff/tmac/tmac.antimes
+9/lib/troff/tmac/tmac.anhtml
+9/lib/troff/tmac/tmac.an
+9/lib/troff/tmac/strings.mm
+9/lib/troff/tmac/sendcover
+9/lib/troff/tmac/name.sed
+9/lib/troff/tmac/mmt
+9/lib/troff/tmac/mmn
+9/lib/troff/tmac/me/thesis.me
+9/lib/troff/tmac/me/tbl.me

Re: ports/138698: lang/php5: PHP session.save_path vulnerability

2009-09-10 Thread remko
Old Synopsis: PHP session.save_path vulnerability
New Synopsis: lang/php5: PHP session.save_path vulnerability

Responsible-Changed-From-To: freebsd-www-freebsd-ports
Responsible-Changed-By: remko
Responsible-Changed-When: Thu Sep 10 10:24:18 UTC 2009
Responsible-Changed-Why: 
reassign to ports team; this has nothing to do with the webmasters queue

http://www.freebsd.org/cgi/query-pr.cgi?pr=138698
___
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/138698: lang/php5: PHP session.save_path vulnerability

2009-09-10 Thread Miroslav Lachman
The following reply was made to PR ports/138698; it has been noted by GNATS.

From: Miroslav Lachman 000.f...@quip.cz
To: bug-follo...@freebsd.org,  andzi...@volt.iem.pw.edu.pl
Cc:  
Subject: Re: ports/138698: lang/php5: PHP session.save_path vulnerability
Date: Thu, 10 Sep 2009 13:14:32 +0200

 I don't know what you are trying to solve.
 
 If PHP runs under user www (Apache), it can still read the content of 
 the directory.
 If you want to disallow access to sessions of different domains 
 (VirtualHosts), you can do it by using different session.save_path for 
 each domain.
 
 In context of VirtualHost for www.domain1.tld:
  php_admin_valuesession.save_path/web/www.domain1.tld/tmp
 
 
 In context of VirtualHost for www.domain2.tld:
  php_admin_valuesession.save_path/web/www.domain2.tld/tmp
___
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


/lib/libz.so version bump prevents java/jdk1* from upgrading

2009-09-10 Thread Alexander Best
hi there,

it would be nice to have a note in UPDATING on how to rebuild an installed
java/jdk1* under = 8. since java/jdk1* requires an installed java environment
in order to build it fails due to the version bump of /lib/libz.so.4 to
/lib/libz.so.5

to be able to rebuild any installed java/jdk1* one needs to install
misc/compat7x. after installation of java/jdk1* finishes misc/compat7x can
safely be deleted (if it's not required by any other port).

i haven't checked what the situation is like when no java environment is
installed, but i believe this doesn't cause a problem since java/diablo-jdk*
is used for bootrapping then.

cheers.
alex
___
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/138698: lang/php5: PHP session.save_path vulnerability

2009-09-10 Thread Maciej Andzinski
The following reply was made to PR ports/138698; it has been noted by GNATS.

From: Maciej Andzinski andzi...@volt.iem.pw.edu.pl
To: Miroslav Lachman 000.f...@quip.cz
Cc: bug-follo...@freebsd.org
Subject: Re: ports/138698: lang/php5: PHP session.save_path vulnerability
Date: Thu, 10 Sep 2009 13:58:42 +0200 (CEST)

 The problem is in permissions and that is what I suggest to fix. Bu you 
 are right, I've made a mistake - the owner of /var/lib/php5 should be 
 root, not www.
 
 I suggest changing permissions to 01733 (rwx-wx-wt), it can prevent 
 session numbers leaking.
 
 Is it clear 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: /lib/libz.so version bump prevents java/jdk1* from upgrading

2009-09-10 Thread Carlos A. M. dos Santos
On Thu, Sep 10, 2009 at 9:00 AM, Alexander
Bestalexbes...@math.uni-muenster.de wrote:

 it would be nice to have a note in UPDATING on how to rebuild an installed
 java/jdk1* under = 8. since java/jdk1* requires an installed java environment
 in order to build it fails due to the version bump of /lib/libz.so.4 to
 /lib/libz.so.5

I agree.

 to be able to rebuild any installed java/jdk1* one needs to install
 misc/compat7x. after installation of java/jdk1* finishes misc/compat7x can
 safely be deleted (if it's not required by any other port).

The compat7x package is not required because libmap.conf does the job. Look at

   http://lists.freebsd.org/pipermail/freebsd-ports/2009-July/056123.html

--
My preferred quotation of Robert Louis Stevenson is You cannot
make an omelette without breaking eggs. Not because I like the
omelettes, but because I like the sound of eggs being broken.
___
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


INDEX build failed for 6.x

2009-09-10 Thread Erwin Lansing
INDEX build failed with errors:
Generating INDEX-6 - please wait..pkg_info: not found
pkg_info: not found
 Done.
make_index: p5-Graphics-Color-0.24: no entry for 
p5-MooseX-Types=0.19/local0/portmgr/tindex/ports/devel/p5-MooseX-Types
make_index: p5-Graphics-Color-0.24: no entry for 
p5-MooseX-Types=0.19/local0/portmgr/tindex/ports/devel/p5-MooseX-Types

Committers on the hook:
gerald roam tobez 

Most recent CVS update was:
U graphics/p5-Graphics-Color/Makefile
U graphics/p5-Graphics-Color/distinfo
U graphics/p5-Graphics-Color/pkg-plist
U lang/gcc44/Makefile
U lang/gcc44/distinfo
U math/p5-Geo-Distance/Makefile
U math/p5-Geo-Distance/distinfo
U security/mhash/Makefile
U security/mhash/distinfo
U security/mhash/files/patch-doc-Makefile.in
U security/mhash/files/patch-include-mutils-mincludes.h
U security/mhash/files/patch-include-mutils-mutils.h
U security/mhash/files/patch-lib-gosthash.c
U security/mhash/files/patch-lib-keygen_mcrypt.c
U security/mhash/files/patch-lib-md5.c
U security/mhash/files/patch-lib-mhash.c
U security/mhash/files/patch-lib-mhash_sha1.c
U security/mhash/files/patch-lib-ripemd.c
U security/mhash/files/patch-lib-sha1.c
U security/mhash/files/patch-lib-sha512_sha384.c
U security/mhash/files/patch-lib-stdfns.c
U security/mhash/files/patch-lib-tiger.c
U security/mhash/files/patch-lib-whirlpool.c
U security/mhash/files/patch-libtool
U security/mhash/files/patch-src-hmac_test.c
U security/mhash/files/patch-src-keygen_test.c
U www/p5-WWW-Curl/Makefile
U www/p5-WWW-Curl/distinfo
U www/p5-WWW-Curl/files/patch-README
U www/p5-WWW-Curl/files/patch-lib-WWW-Curl.pm
___
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: /lib/libz.so version bump prevents java/jdk1* from upgrading

2009-09-10 Thread Alexander Best
thanks for the hint. i was actually aware of this thread and the way of fixing
the problem described in it. however from a users perspective i think
installing a port to fix this problem is much more easy and convenient than to
hack in any changes to /etc/libmap.conf. don't you agree?

cheers.
alex

Maciej Suszko schrieb am 2009-09-10:
 Alexander Best alexbes...@math.uni-muenster.de wrote:
  hi there,

  it would be nice to have a note in UPDATING on how to rebuild an
  installed java/jdk1* under = 8. since java/jdk1* requires an
  installed java environment in order to build it fails due to the
  version bump of /lib/libz.so.4 to /lib/libz.so.5

  to be able to rebuild any installed java/jdk1* one needs to install
  misc/compat7x. after installation of java/jdk1* finishes
  misc/compat7x can safely be deleted (if it's not required by any
  other port).

  i haven't checked what the situation is like when no java
  environment
  is installed, but i believe this doesn't cause a problem since
  java/diablo-jdk* is used for bootrapping then.

 Add those lines in /etc/libmap.conf (this is for jdk16):
 [/usr/local/jdk1.6.0/]
 libz.so.4  libz.so.5

 Than you can rebuild your jdk.
___
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: /lib/libz.so version bump prevents java/jdk1* from upgrading

2009-09-10 Thread Wesley Shields
On Thu, Sep 10, 2009 at 03:10:17PM +0200, Alexander Best wrote:
 thanks for the hint. i was actually aware of this thread and the way
 of fixing the problem described in it. however from a users
 perspective i think installing a port to fix this problem is much more
 easy and convenient than to hack in any changes to /etc/libmap.conf.
 don't you agree?

I'd submit a PR or contact the maintainer directly. It shouldn't be too
hard to add compat7x as a build dependency.

-- WXS
___
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: /lib/libz.so version bump prevents java/jdk1* from upgrading

2009-09-10 Thread Maciej Suszko
Alexander Best alexbes...@math.uni-muenster.de wrote:
 hi there,
 
 it would be nice to have a note in UPDATING on how to rebuild an
 installed java/jdk1* under = 8. since java/jdk1* requires an
 installed java environment in order to build it fails due to the
 version bump of /lib/libz.so.4 to /lib/libz.so.5
 
 to be able to rebuild any installed java/jdk1* one needs to install
 misc/compat7x. after installation of java/jdk1* finishes
 misc/compat7x can safely be deleted (if it's not required by any
 other port).
 
 i haven't checked what the situation is like when no java environment
 is installed, but i believe this doesn't cause a problem since
 java/diablo-jdk* is used for bootrapping then.

Add those lines in /etc/libmap.conf (this is for jdk16):
[/usr/local/jdk1.6.0/]
libz.so.4  libz.so.5

Than you can rebuild your jdk.
-- 
regards, Maciej Suszko.


signature.asc
Description: PGP signature


Re: /lib/libz.so version bump prevents java/jdk1* from upgrading

2009-09-10 Thread Maciej Suszko
Alexander Best alexbes...@math.uni-muenster.de wrote:
 thanks for the hint. i was actually aware of this thread and the way
 of fixing the problem described in it. however from a users
 perspective i think installing a port to fix this problem is much
 more easy and convenient than to hack in any changes
 to /etc/libmap.conf. don't you agree?

I'm not sure if some bins/libs wouldn't be linked against those present
in compat7x package in case when you forget to remove it after jdk
upgrade. In my opinion using libmap.conf is more convenient, especially
in this situation, when the whole jdk installation is done within one
directory under /usr/local.
-- 
regards, Maciej Suszko.


signature.asc
Description: PGP signature


INDEX now builds successfully on 6.x

2009-09-10 Thread Erwin Lansing

___
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: /lib/libz.so version bump prevents java/jdk1* from upgrading

2009-09-10 Thread Alexander Best
submitted a PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=138706

thanks everybody.

alex

Wesley Shields schrieb am 2009-09-10:
 On Thu, Sep 10, 2009 at 03:10:17PM +0200, Alexander Best wrote:
  thanks for the hint. i was actually aware of this thread and the
  way
  of fixing the problem described in it. however from a users
  perspective i think installing a port to fix this problem is much
  more
  easy and convenient than to hack in any changes to
  /etc/libmap.conf.
  don't you agree?

 I'd submit a PR or contact the maintainer directly. It shouldn't be
 too
 hard to add compat7x as a build dependency.

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


amavisd-new crashing

2009-09-10 Thread Eric Sheesley


For the past week or so I've had 2-3 different emails that, as they  
are attempting to be delivered end up crashing amavisd-new(just one  
instance, not the whole daemon) leading the the error:  queue file  
write error from postfix.  Both messages appear to have been 8bitmime  
encoded from a quick glance, but no other common points.  These emails  
will continually crash amavis every 15 minutes as the servers attempt  
delivery.  I've used portmanager to rebuild amavis and all  
dependencies with no change.  Any ideas on what could be wrong?

___
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/138698: lang/php5: PHP session.save_path vulnerability

2009-09-10 Thread Miroslav Lachman
The following reply was made to PR ports/138698; it has been noted by GNATS.

From: Miroslav Lachman 000.f...@quip.cz
To: bug-follo...@freebsd.org,  andzi...@volt.iem.pw.edu.pl
Cc:  
Subject: Re: ports/138698: lang/php5: PHP session.save_path vulnerability
Date: Thu, 10 Sep 2009 20:49:14 +0200

 Yes, it is clear now and with owner root, it works.
 
 I propose to make this optional, as somebody has /tmp optimized for 
 better speed (another disk device, flash device, RAM disk etc.) but not 
 /var/lib/php5.
 And FreeBSD doesn't have /var/lib by default. /var/lib/* is mostly used 
 by some Linux distributions). I am not sure if it is the right place to 
 put these files, according to man hier(7).
 Next thing to think about is, that /tmp is (or easily can be) cleared at 
 system startup, but /var/*/* not.
 If we do some change in default php.ini, it affects more then just 
 files are moved to another place, so things need to be done carefully.
 
 Maybe leave the default as is and put these hardening steps in comments 
 in php.ini, then anybody can make own decision.
___
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/138698: lang/php5: PHP session.save_path vulnerability

2009-09-10 Thread piotr . smyrak
On Thu, 10 Sep 2009 18:50:02 GMT, Miroslav Lachman wrote
 The following reply was made to PR ports/138698; it has 
 been noted by GNATS.
 
 From: Miroslav Lachman 000.f...@quip.cz
 To: bug-follo...@freebsd.org,  andzi...@volt.iem.pw.edu.pl
 Cc:  
 Subject: Re: ports/138698: lang/php5: PHP 
 session.save_path vulnerability
 Date: Thu, 10 Sep 2009 20:49:14 +0200
 
  Yes, it is clear now and with owner root, it works.
 
  I propose to make this optional, as somebody has /tmp 
 optimized for  better speed (another disk device, flash 
 device, RAM disk etc.) but not  /var/lib/php5. And FreeBSD 
 doesn't have /var/lib by default. /var/lib/* is mostly 
 used  by some Linux distributions). I am not sure if it is 
 the right place to  put these files, according to man 
 hier(7). Next thing to think about is, that /tmp is (or 
 easily can be) cleared at  system startup, but /var/*/* 
 not. If we do some change in default php.ini, it affects 
 more then just  files are moved to another place, so 
 things need to be done carefully.
 
  Maybe leave the default as is and put these hardening 
 steps in comments  in php.ini, then anybody can make own decision.

UPDATING msg would be in place, too IMO.

-- 
 Piotr Smyrak
 piotr.smy...@heron.pl

___
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: amavisd-new crashing

2009-09-10 Thread Per olof Ljungmark

Eric Sheesley wrote:


For the past week or so I've had 2-3 different emails that, as they are 
attempting to be delivered end up crashing amavisd-new(just one 
instance, not the whole daemon) leading the the error:  queue file 
write error from postfix.  Both messages appear to have been 8bitmime 
encoded from a quick glance, but no other common points.  These emails 
will continually crash amavis every 15 minutes as the servers attempt 
delivery.  I've used portmanager to rebuild amavis and all dependencies 
with no change.  Any ideas on what could be wrong?


Hi,

Both amavis and Postfix can be made to provide rather substantial 
logging, that's what I would have done in your case. Or do you already 
have some logs to share?


Also, did you check that you did not run out of memory?

HTH,

--
per
___
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 Port: snort-2.8.4.1_1

2009-09-10 Thread Joseph Bruni

Hello,

Could you update the snort port to expose the --enable-ipv6 build  
option to the config phase?


Regards,
Joe Bruni



Re: amavisd-new crashing

2009-09-10 Thread Eric Sheesley
Here is one sample of the log(level 5 logging on).  not very descriptive
about the problem, at least i don't see it.

Sep 10 19:00:07 rogue postfix/smtpd[77645]: connect from
tx2ehsobe003.messaging.microsoft.com[65.55.88.13]
Sep 10 19:00:07 rogue postfix/smtpd[77645]: NOQUEUE:
client=tx2ehsobe003.messaging.microsoft.com[65.55.88.13]
Sep 10 19:00:08 rogue amavis[77712]: (77712-01) ESMTP::10024
/var/amavis/tmp/amavis-20090910T190007-77712: froma...@fromaddr.com -
mya...@shadowlair.com SIZE=7072 BODY=7BIT Received: from
rogue.shadowlair.com ([127.0.0.1]) by localhost (rogue.shadowlair.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP for
eshee...@shadowlair.com; Thu, 10 Sep 2009 19:00:07 -0400 (EDT)
Sep 10 19:00:08 rogue amavis[77712]: (77712-01) Checking: SukXX+6vDV2U
[65.55.88.13] froma...@fromaddr.com - mya...@shadowlair.com
Sep 10 19:00:08 rogue amavis[77712]: (77712-01) p001 1 Content-Type:
text/plain, size: 3607 B, name:
Sep 10 19:00:08 rogue postfix/smtpd[77645]: warning: lost connection
with proxy 127.0.0.1:10024
Sep 10 19:00:08 rogue amavis[78041]: TIMING [total 5 ms] - bdb-open: 5
(100%)100, rundown: 0 (0%)100
Sep 10 19:00:08 rogue postfix/cleanup[78042]: 4EDE850837:
message-id=20090910230008.4ede850...@rogue.shadowlair.com
Sep 10 19:00:08 rogue postfix/smtpd[77645]: disconnect from
tx2ehsobe003.messaging.microsoft.com[65.55.88.13]


Per olof Ljungmark wrote:
 Eric Sheesley wrote:

 For the past week or so I've had 2-3 different emails that, as they
 are attempting to be delivered end up crashing amavisd-new(just one
 instance, not the whole daemon) leading the the error:  queue file
 write error from postfix.  Both messages appear to have been 8bitmime
 encoded from a quick glance, but no other common points.  These emails
 will continually crash amavis every 15 minutes as the servers attempt
 delivery.  I've used portmanager to rebuild amavis and all
 dependencies with no change.  Any ideas on what could be wrong?
 
 Hi,
 
 Both amavis and Postfix can be made to provide rather substantial
 logging, that's what I would have done in your case. Or do you already
 have some logs to share?
 
 Also, did you check that you did not run out of memory?
 
 HTH,
 
 -- 
 per
___
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: amavisd-new crashing

2009-09-10 Thread Eric Sheesley
Actually, the directory is set to vscan as it should be(amavis runs as
that) and that user has rw privs.  If you notice below, the pid of the
processes is different between the area where content-type is mentioned
and the bdb is referenced.  For some reason there is a very brutal crash
before any real checks are run.

I've rebuilt amavis and all dependencies using portmanager with no
change.  Any other thoughts or methods of debugging.  One of the emails
causing this was sent by a friend, so not even malicious, just causing a
crash.

Chuck Swiger wrote:
 Hi--
 
 On Sep 10, 2009, at 4:23 PM, Eric Sheesley wrote:
 Sep 10 19:00:08 rogue amavis[77712]: (77712-01) ESMTP::10024
 /var/amavis/tmp/amavis-20090910T190007-77712: froma...@fromaddr.com -
 mya...@shadowlair.com SIZE=7072 BODY=7BIT Received: from
 rogue.shadowlair.com ([127.0.0.1]) by localhost (rogue.shadowlair.com
 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP for
 eshee...@shadowlair.com; Thu, 10 Sep 2009 19:00:07 -0400 (EDT)
 Sep 10 19:00:08 rogue amavis[77712]: (77712-01) Checking: SukXX+6vDV2U
 [65.55.88.13] froma...@fromaddr.com - mya...@shadowlair.com
 Sep 10 19:00:08 rogue amavis[77712]: (77712-01) p001 1 Content-Type:
 text/plain, size: 3607 B, name:
 Sep 10 19:00:08 rogue postfix/smtpd[77645]: warning: lost connection
 with proxy 127.0.0.1:10024
 Sep 10 19:00:08 rogue amavis[78041]: TIMING [total 5 ms] - bdb-open: 5
 (100%)100, rundown: 0 (0%)100
 
 It sounds like amavisd can't open a BerkeleyDB database (probably the
 nanny/cache/snmp stuff).  Make sure that /var/amavis/db exists and is
 writable by the amavisd or vscan user, whatever you are running amavisd as:
 
 # ls -l /var/amavis/db
 total 556
 -rw-r-  1 vscan  vscan   24576 Sep  9 19:01 __db.001
 -rw-r-  1 vscan  vscan  131072 Sep  9 18:44 __db.002
 -rw-r-  1 vscan  vscan  270336 Sep 10 11:43 __db.003
 -rw-r-  1 vscan  vscan  360448 Sep  9 18:44 __db.004
 -rw-r-  1 vscan  vscan4096 Sep  9 14:20 cache-expiry.db
 -rw-r-  1 vscan  vscan   90112 Sep 10 14:01 cache.db
 -rw-r-  1 vscan  vscan   12288 Sep  9 14:20 nanny.db
 -rw-r-  1 vscan  vscan   12288 Sep  9 14:20 snmp.db
 
 Regards,
___
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: amavisd-new crashing

2009-09-10 Thread Eric Sheesley
Another sample attached:

Sep 10 20:15:41 rogue postfix/smtpd[59483]: connect from
mail-vw0-f180.google.com[209.85.212.180]
Sep 10 20:15:41 rogue postfix/smtpd[59483]: NOQUEUE:
client=mail-vw0-f180.google.com[209.85.212.180]
Sep 10 20:15:41 rogue amavis[77720]: (77720-02) ESMTP::10024
/var/amavis/tmp/amavis-20090910T192517-77720: deadsen...@gmail.com -
e...@shadowlair.com Received: from rogue.shadowlair.com ([127.0.0.1])
by localhost (rogue.shadowlair.com [127.0.0.1]) (amavisd-new, port
10024) with ESMTP for mya...@shadowlair.com; Thu, 10 Sep 2009 20:15:41
-0400 (EDT)
Sep 10 20:15:41 rogue amavis[77720]: (77720-02) dkim: VALID
Author+Sender+MailFrom signature by i...@gmail.com, From:
deadsen...@gmail.com, a=rsa-sha256, c=relaxed/relaxed, s=gamma,
d=gmail.com
Sep 10 20:15:41 rogue amavis[77720]: (77720-02) dkim: VALID
Author+Sender+MailFrom signature by i=deadsen...@gmail.com, From:
deadsen...@gmail.com, a=rsa-sha1, c=nofws, s=gamma, d=gmail.com
Sep 10 20:15:41 rogue amavis[77720]: (77720-02) Checking: 2UIxlfrQ4TAm
[209.85.212.180] deadsen...@gmail.com - mya...@shadowlair.com
Sep 10 20:15:41 rogue amavis[77720]: (77720-02) p003 1 Content-Type:
multipart/alternative
Sep 10 20:15:41 rogue amavis[77720]: (77720-02) p001 1/1 Content-Type:
text/plain, size: 3383 B, name:
Sep 10 20:15:41 rogue amavis[77720]: (77720-02) p002 1/2 Content-Type:
text/html, size: 5031 B, name:
Sep 10 20:15:41 rogue postfix/smtpd[59483]: warning: lost connection
with proxy 127.0.0.1:10024
Sep 10 20:15:41 rogue amavis[59998]: TIMING [total 6 ms] - bdb-open: 6
(100%)100, rundown: 0 (0%)100
Sep 10 20:15:41 rogue postfix/cleanup[59992]: 8EA9F5083B:
message-id=20090911001541.8ea9f50...@rogue.shadowlair.com
Sep 10 20:15:41 rogue postfix/smtpd[59483]: disconnect from
mail-vw0-f180.google.com[209.85.212.180]


Chuck Swiger wrote:
 Hi--
 
 On Sep 10, 2009, at 4:23 PM, Eric Sheesley wrote:
 Sep 10 19:00:08 rogue amavis[77712]: (77712-01) ESMTP::10024
 /var/amavis/tmp/amavis-20090910T190007-77712: froma...@fromaddr.com -
 mya...@shadowlair.com SIZE=7072 BODY=7BIT Received: from
 rogue.shadowlair.com ([127.0.0.1]) by localhost (rogue.shadowlair.com
 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP for
 eshee...@shadowlair.com; Thu, 10 Sep 2009 19:00:07 -0400 (EDT)
 Sep 10 19:00:08 rogue amavis[77712]: (77712-01) Checking: SukXX+6vDV2U
 [65.55.88.13] froma...@fromaddr.com - mya...@shadowlair.com
 Sep 10 19:00:08 rogue amavis[77712]: (77712-01) p001 1 Content-Type:
 text/plain, size: 3607 B, name:
 Sep 10 19:00:08 rogue postfix/smtpd[77645]: warning: lost connection
 with proxy 127.0.0.1:10024
 Sep 10 19:00:08 rogue amavis[78041]: TIMING [total 5 ms] - bdb-open: 5
 (100%)100, rundown: 0 (0%)100
 
 It sounds like amavisd can't open a BerkeleyDB database (probably the
 nanny/cache/snmp stuff).  Make sure that /var/amavis/db exists and is
 writable by the amavisd or vscan user, whatever you are running amavisd as:
 
 # ls -l /var/amavis/db
 total 556
 -rw-r-  1 vscan  vscan   24576 Sep  9 19:01 __db.001
 -rw-r-  1 vscan  vscan  131072 Sep  9 18:44 __db.002
 -rw-r-  1 vscan  vscan  270336 Sep 10 11:43 __db.003
 -rw-r-  1 vscan  vscan  360448 Sep  9 18:44 __db.004
 -rw-r-  1 vscan  vscan4096 Sep  9 14:20 cache-expiry.db
 -rw-r-  1 vscan  vscan   90112 Sep 10 14:01 cache.db
 -rw-r-  1 vscan  vscan   12288 Sep  9 14:20 nanny.db
 -rw-r-  1 vscan  vscan   12288 Sep  9 14:20 snmp.db
 
 Regards,
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Port Maintainer Support List

2009-09-10 Thread Tim Gustafson
Is there a port maintainer's support list?

I'd like to contribute a port, but I'm not all that savvy when it comes to this 
stuff, and it'd be nice to have some support in that regard.

Thanks!

Tim Gustafson
Baskin School of Engineering
UC Santa Cruz
t...@soe.ucsc.edu
831-459-5354

___
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 Maintainer Support List

2009-09-10 Thread Tim Gustafson
 Is there a port maintainer's support list?

Doh!  Please disregard this.  I answered my own question about 30 seconds after 
sending the hey, is there a ports maintainer list question.

Tim Gustafson
Baskin School of Engineering
UC Santa Cruz
t...@soe.ucsc.edu
831-459-5354
___
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


Creating a New Port: /usr/ports/security/pecl-kadm5

2009-09-10 Thread Tim Gustafson
I'm trying to create a new port.  To get myself started, I copied pecl-hash and 
then modified the Makefile and the distinfo file.  When I try to make my port, 
it downloads the file from the PECL repository, extracts it, runs configure and 
then starts compiling, but in the end I get a bunch of errors from cc about 
undefined constants:

kadm5.c: In function 'kadm5_error':
kadm5.c:285: error: 'KADM5_FAILURE' undeclared (first use in this function)
kadm5.c:285: error: (Each undeclared identifier is reported only once
kadm5.c:285: error: for each function it appears in.)
kadm5.c:288: error: 'KADM5_AUTH_GET' undeclared (first use in this function)
kadm5.c:291: error: 'KADM5_AUTH_ADD' undeclared (first use in this function)

So, I manually edited work/kadm5-0.2.3/kadm5.c and added:

#include kadm5/kadm5_err.h

That file has -most- of the needed declarations, but there are a few more that 
aren't there, and I'm thinking the version of Kerberos that's installed in 
FreeBSD 7.2 just doesn't have those declarations (the two missing declarations 
are for KADM5_AUTH_SETKEY and KADM5_SETKEY_DUP_ENCTYPES).

So, my first question is: How can I tell my port to patch 
work/kadm5-0.2.3/kadm5.c with the needed line above?

My second question is: Is there a proper way to hack the needed values into 
kadm5_err.h?  Should I make a new .h file and include it as part of the port 
only?

And last but not least:

After I manually patched the kadm5.c file and hacked the missing declarations 
into kadm5_err.h, I get a different set of errors:

kadm5.c: In function 'kadm5_error':
kadm5.c:440: error: label at end of compound statement
kadm5.c: In function 'zif_kadm5_get_principals':
kadm5.c:1048: warning: passing argument 3 of 'kadm5_free_name_list' makes 
pointer from integer without a cast
kadm5.c: In function 'zif_kadm5_get_policies':
kadm5.c:1184: warning: passing argument 3 of 'kadm5_free_name_list' makes 
pointer from integer without a cast

Now, I am not a C programmer.  I took a C class in about 1996 and that's more 
or less the last I've done in C.  Is there anyone out there who might be kind 
enough to help me get this port working?  I have a real need for Kerberos 
administration from within PHP, and this PECL library being absent has been a 
stumbling block for a long time now.

Tim Gustafson
Baskin School of Engineering
UC Santa Cruz
t...@soe.ucsc.edu
831-459-5354

___
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: Creating a New Port: /usr/ports/security/pecl-kadm5

2009-09-10 Thread Glen Barber

Hi.

On Thu, 10 Sep 2009 20:36:25 -0400, Tim Gustafson t...@soe.ucsc.edu wrote:

I'm trying to create a new port.  To get myself started, I copied  
pecl-hash and then modified the Makefile and the distinfo file.  When I  
try to make my port, it downloads the file from the PECL repository,  
extracts it, runs configure and then starts compiling, but in the end I  
get a bunch of errors from cc about undefined constants:


[snip]

So, my first question is: How can I tell my port to patch  
work/kadm5-0.2.3/kadm5.c with the needed line above?




You will want to create a '-patch' line in the Makefile.  See the  
following as a reference:


http://www.freebsd.org/doc/en/books/porters-handbook/slow-patch.html

My second question is: Is there a proper way to hack the needed values  
into kadm5_err.h?  Should I make a new .h file and include it as part of  
the port only?




You can create a ${PORTNAME}/files directory containing the file(s) you  
need, specific to your port and FreeBSD.


See the following link for more information:

http://www.freebsd.org/doc/en/books/porters-handbook/install.html


And last but not least:

After I manually patched the kadm5.c file and hacked the missing  
declarations into kadm5_err.h, I get a different set of errors:




[snip]

Sorry.  There are lots of experienced folks who can help with C errors.   
I, unfortunately, am not one of them.


You may want to bookmark this, as well:

http://www.freebsd.org/doc/en/books/porters-handbook/

Cheers,

--
Glen Barber
___
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: amavisd-new crashing

2009-09-10 Thread Chuck Swiger

Hi--

On Sep 10, 2009, at 4:23 PM, Eric Sheesley wrote:

Sep 10 19:00:08 rogue amavis[77712]: (77712-01) ESMTP::10024
/var/amavis/tmp/amavis-20090910T190007-77712:  
froma...@fromaddr.com -

mya...@shadowlair.com SIZE=7072 BODY=7BIT Received: from
rogue.shadowlair.com ([127.0.0.1]) by localhost (rogue.shadowlair.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP for
eshee...@shadowlair.com; Thu, 10 Sep 2009 19:00:07 -0400 (EDT)
Sep 10 19:00:08 rogue amavis[77712]: (77712-01) Checking: SukXX+6vDV2U
[65.55.88.13] froma...@fromaddr.com - mya...@shadowlair.com
Sep 10 19:00:08 rogue amavis[77712]: (77712-01) p001 1 Content-Type:
text/plain, size: 3607 B, name:
Sep 10 19:00:08 rogue postfix/smtpd[77645]: warning: lost connection
with proxy 127.0.0.1:10024
Sep 10 19:00:08 rogue amavis[78041]: TIMING [total 5 ms] - bdb-open: 5
(100%)100, rundown: 0 (0%)100


It sounds like amavisd can't open a BerkeleyDB database (probably the  
nanny/cache/snmp stuff).  Make sure that /var/amavis/db exists and is  
writable by the amavisd or vscan user, whatever you are running  
amavisd as:


# ls -l /var/amavis/db
total 556
-rw-r-  1 vscan  vscan   24576 Sep  9 19:01 __db.001
-rw-r-  1 vscan  vscan  131072 Sep  9 18:44 __db.002
-rw-r-  1 vscan  vscan  270336 Sep 10 11:43 __db.003
-rw-r-  1 vscan  vscan  360448 Sep  9 18:44 __db.004
-rw-r-  1 vscan  vscan4096 Sep  9 14:20 cache-expiry.db
-rw-r-  1 vscan  vscan   90112 Sep 10 14:01 cache.db
-rw-r-  1 vscan  vscan   12288 Sep  9 14:20 nanny.db
-rw-r-  1 vscan  vscan   12288 Sep  9 14:20 snmp.db

Regards,
--
-Chuck

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


Re: devel/9base v2 upgrade to v4

2009-09-10 Thread Jason J. Hellenthal

On Thu, 10 Sep 2009 04:24 -, sbrabez wrote:


Hi Jason

On Wed, Sep 9, 2009 at 6:10 PM, Jason J. Hellenthal jas...@dataix.net wrote:


Would it be possible to fit in 9base-4 before the ports freeze. I am
planning on going off air within the next couple of weeks and this is my
preferred window manager and the provided with 9base-4 read command sure
would come in handy.

http://dl.suckless.org/tools/9base-4.tar.gz

Thanks in advance.

--

 |-|

 Jason J. Hellenthal
 http://www.DataIX.net/
 jas...@dataix.net
 0x691411AC

 - (2^(N-1))



I prefer wait the port freeze of 14 September to update devel/9base but as you
need it. I attached a unified diff which allow you to compile and install the
new version 9base-4 released the 2009/09/27.

As you could see, It needs lot of changes because lot of new binaries are now
in plan9port distribution. That's why I want to wait the port freeze to
correct handle them.

Regards



Thank you very much, This is much appreciated.

As a workaround I have been just doing a local compile of 9lib and read then 
just copying the resulting read static binary to local/9/bin. Though this has 
provided temporary fixes its a pretty tedious process.


Curious question:

Have you noticed any weirdness the user environment whether it be in X or on the
console while the fdescfs module is loaded ?. I have had some impacts with this
being loaded in the past that I can not really explain and has deterred me from 
wanting to use the environment with that module loaded. I have noticed this 
happening since 6.1 through 7.2-STABLE and not specific to just the wmii port.


Best regards. And thanks again.

--

 ||

 Jason J. Hellenthal
 http://www.DataIX.net/
 jas...@dataix.net
 0x691411AC

 - (2^(N-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


audio/sox bump to 14.3.0 request

2009-09-10 Thread Peter Beckman

I haven't heard back from the maintainer of sox yet on the requested bump
to sox 14.3.0.  I didn't find any process outlined in the handbook or the
porters handbook, and I would have searched the archives but the search
index hasn't been rebuilt since 2007.

I searched the archives via google with no real results on any process on
how to poke the maintainer to life.

ports/138248: audio/sox bump to 14.3.0 (actual title is wrong)

Anyone seen Dan Nelson?

---
Peter Beckman  Internet Guy
beck...@angryox.com http://www.angryox.com/
---
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: audio/sox bump to 14.3.0 request

2009-09-10 Thread Glen Barber

Hi.


On Thu, 10 Sep 2009 21:31:53 -0400, Peter Beckman beck...@angryox.com  
wrote:



I haven't heard back from the maintainer of sox yet on the requested bump
to sox 14.3.0.  I didn't find any process outlined in the handbook or the
porters handbook, and I would have searched the archives but the search
index hasn't been rebuilt since 2007.



Regarding ports that are maintained, there is generally a 2 week timeout  
with PRs regarding port upgrades (which is noted in the handbook),  
assuming a patch is provided.  The most likely delay with your situation  
is that you did not support a patch to actually perform the update -  
simply the request.  Upgrading ports that has other maintainers is time  
consuming to begin with - even moreso when you do not provide a patch to  
aide in the process.



I searched the archives via google with no real results on any process on
how to poke the maintainer to life.



You CC'd the maintainer.  That is sufficient.


--
Glen Barber
___
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: audio/sox bump to 14.3.0 request

2009-09-10 Thread Peter Beckman

On Thu, 10 Sep 2009, Glen Barber wrote:

On Thu, 10 Sep 2009 21:31:53 -0400, Peter Beckman beck...@angryox.com 
wrote:



I haven't heard back from the maintainer of sox yet on the requested bump
to sox 14.3.0.  I didn't find any process outlined in the handbook or the
porters handbook, and I would have searched the archives but the search
index hasn't been rebuilt since 2007.



Regarding ports that are maintained, there is generally a 2 week timeout with 
PRs regarding port upgrades (which is noted in the handbook), assuming a 
patch is provided.  The most likely delay with your situation is that you did 
not support a patch to actually perform the update - simply the request. 
Upgrading ports that has other maintainers is time consuming to begin with - 
even moreso when you do not provide a patch to aide in the process.



I searched the archives via google with no real results on any process on
how to poke the maintainer to life.



You CC'd the maintainer.  That is sufficient.


 Awesome, thanks Glen.  I didn't see the 2 week timeout in the handbook,
 must have missed it.  I'll work on learning how to build the package so I
 can submit a diff rather than a request.

Beckman
---
Peter Beckman  Internet Guy
beck...@angryox.com http://www.angryox.com/
---
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: audio/sox bump to 14.3.0 request

2009-09-10 Thread Glen Barber
On Thu, 10 Sep 2009 22:01:00 -0400, Peter Beckman beck...@angryox.com  
wrote:
I'll work on learning how to build the package so I can submit a diff  
rather than a request.


The Porter's Handbook is a good place to start:

http://www.freebsd.org/doc/en/books/porters-handbook/

The Handbook recommends the ports-mgmt/porttools port.  I personally  
suggest the ports-mgmt/genplist port as well.


Cheers,

--
Glen Barber
___
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


Upgraded Trac, but still getting errors...

2009-09-10 Thread Christopher J. Umina

Hi,

I noticed recently (probably due to me upgrading ports) that my trac 
installations show this message:


*Warning:* Can't synchronize with the repository (Couldn't open 
Subversion repository /var/svn/repo: SubversionException: ('SQLite 
compiled for 3.6.14.2, but running with 3.3.7', 200030)). Look in the 
Trac log for more information.


The first thing I did was check the trac logs, which literally show 
nothing at all.  Next thing I did was Google the error message, but 
nothing really matched.  After that I decided to rebuild trac and deps 
(portupgrade -rR), which didn't fix the problem.  I then got frustrated 
and ran a portupgrade -fa, which again didn't fix the problem.  I 
upgraded python from python25 to python26, using the procedure outlined 
in /usr/ports/UPDATING which didn't fix the problem either.


Through all this, I did notice that if I run tracd on the environment, 
the errors are gone and I can interact with subversion (through trac) 
perfectly.  For that reason, I'm convinced it's something to do with 
Apache  friends, but I'm completely out of ideas, has anybody else seen 
these errors or have any suggestions?


Packages (worth mentioning) currently installed:
trac-0.11.5
subversion-1.6.5
python26-2.6.2_2
py26-pysqlite-2.3.5
py26-sqlite3-2.6.2_1
sqlite3-3.6.14.2
mod_python-3.3.1_2
apache-2.2.13

Thank you,
Christopher J. Umina
___
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: audio/sox bump to 14.3.0 request

2009-09-10 Thread Charlie Kester

On Thu 10 Sep 2009 at 19:01:23 PDT Glen Barber wrote:
On Thu, 10 Sep 2009 22:01:00 -0400, Peter Beckman 
beck...@angryox.com wrote:
I'll work on learning how to build the package so I can submit a 
diff rather than a request.


The Porter's Handbook is a good place to start:

http://www.freebsd.org/doc/en/books/porters-handbook/

The Handbook recommends the ports-mgmt/porttools port.  I personally
suggest the ports-mgmt/genplist port as well.


I would also recommend installing the ports-mgmt/tinderbox port as well.
Some of my first few patches were bounced back by the committers because
of build problems that were masked by software that was installed on my
machine but not called out as a dependency in the port Makefile.  I
learned to always test the port in a tinderbox jail before submitting a
PR with the patch.  There should not be any error logs generated, but
you should also check the build logs to verify that everything your port
installs gets deinstalled in the deinstall phase.

___
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