Unfetchable distfiles reminder

2007-03-07 Thread Bill Fenner

Dear porters,

  This is just a reminder to please periodically check the list of
unfetchable distfiles at http://people.freebsd.org/~fenner/portsurvey/ .
In particular, the list of ports with no MAINTAINER with distfile
problems, which currently has 228 bad ports, is

http://people.freebsd.org/~fenner/portsurvey/[EMAIL PROTECTED]

Since no one is responsible for these ports, the problem won't get
fixed unless someone on this list takes the initiative.

  In addition, the list of all ports with any unfetchable distfile is

http://people.freebsd.org/~fenner/portsurvey/bad.html

if you don't mind coordinating your fixes with the port MAINTAINER.

Thanks for your help!

Bill distfiles Fenner
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FreeBSD ports: 1 unfetchable distfile: net/py-impacket

2007-03-07 Thread Marcin Jessa
On Wednesday 07 March 2007 11:01, Bill distfiles Fenner wrote:
 Dear [EMAIL PROTECTED],

   You are listed as the FreeBSD port maintainer for 1 port
 whose distfiles are not fetchable from their MASTER_SITES.  Could
 you please visit

 http://people.freebsd.org/~fenner/portsurvey/[EMAIL PROTECTED]

 and correct the problems listed there?  The individual port with
 a problem is net/py-impacket.

The taball is there together with older versions:
http://oss.coresecurity.com/repo/Impacket-0.9.6.0.tar.gz
http://www.yazzy.org/ports/impacket/Impacket-0.9.6.0.tar.gz

The script checking this must have had a bad day :)

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


Whats this: UPDATING 2007030

2007-03-07 Thread Heino Tiedemann
,
| 20070301:
|   AFFECTS: users of ports-mgmt/portupgrade*
|   AUTHOR: [EMAIL PROTECTED]
| 
|   Because of a bug in previous version, it's recomended you fill ALT_PKGDEP
|   section in pkgtools.conf file for portupgrade be aware of alternative
|   dependencies you use, and run pkgdb -L to restore dependencies that was
|   lost.
| 
|   Example of ALT_PKGDEP section:
|   ALT_PKGDEP = {
| 'www/apache13' = 'www/apache13-modssl',
| 'print/ghostscript-afpl' = 'print/ghostscript-gnu',
|   }
| 
|   Note also, portupgrade knows nothing how to handle ports with different
|   suffixes (E.g. -nox11). So you should define explicitly variables 
|   (E.g. WITHOUT_X11=yes) for the ports in /etc/make.conf or pkgtools.conf
|   (MAKE_ARGS section) files.
`


Hi,

sorry I do not understand, WHAT to do there.

Okay, there is an example, but what doas this mean concretely to me?

Does that mean, that I am responsible für all deps in ports? 
That cannot be? is it?

Heino

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


Re: FreeBSD ports: 1 unfetchable distfile: net/py-pypcap

2007-03-07 Thread tmclaugh
 At Tue, 6 Mar 2007 18:24:12 - (UTC),
 [EMAIL PROTECTED] wrote:
 The author moved the project over to googlecode.com.  I updated the port
 and pointed it over to that site.


 Ah, but here is the problem.  I have updated the package for use with
 PCS, and Doug Song has not as yet added those bits.  This is kinda a
 fork, but I am feeding him the changes etc.  Can we either:

 1) update the PCS port to grab my version

I think this is the ideal way to handle the situation.  Only caveat on
your end is your modified pypcap shouldn't interfere with the port of
Doug's pypcap.  It should install with a slightly different module name so
we don't need to set port conflicts and so ports relying on net/pypcap
don't see your fork installed and assume net/py-pypcap is installed which
may lead to potential breakage.

 or

 2) change the py-pypcap port to point to my version?

Additionally, if these changes have been accepted by Doug and you're just
waiting for him to do a new release you could just add your patches to the
port's patch files.  It sounds like you'll be continuing work on your
pypcap fork so I don't think this option is as preferable as the first.

 I suspect 1 is the more polite way to go?

 Sorry for the confusion.

 Later,
 George


tom

-- 
| tmclaugh at sdf.lonestar.org tmclaugh at FreeBSD.org |
| FreeBSD   http://www.FreeBSD.org |
| BSD#http://www.mono-project.com/Mono:FreeBSD |

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


Re: Whats this: UPDATING 2007030

2007-03-07 Thread Kirill Ponomarew
On Wed, Mar 07, 2007 at 09:42:00PM +0300, Sergey Matveychuk wrote:
 Heino Tiedemann wrote:
  
  sorry I do not understand, WHAT to do there.
  
  Okay, there is an example, but what doas this mean concretely to me?
  
  Does that mean, that I am responsible fur all deps in ports? 
  That cannot be? is it?
  
 
 I think you can just ignore it if you don't understand. It's safe in the
 case. Do not run pkgdb -L. Dependencies will restore after a few upgrades.

Hmm, it seems portupgrade-devel is broken eg:

# portupgrade p5-Compress-Raw-Zlib-2.003
[Gathering depends for archivers/p5-Compress-Raw-Zlib
./usr/local/sbin/portupgrade:842:in `get_all_depends': undefined
method `compact' for #Set: {} (NoMethodError)
from /usr/local/sbin/portupgrade:833:in `get_all_depends'
from /usr/local/lib/ruby/1.8/set.rb:189:in `each'
from /usr/local/lib/ruby/1.8/set.rb:189:in `each_key'
from /usr/local/lib/ruby/1.8/set.rb:189:in `each'
from /usr/local/sbin/portupgrade:832:in `get_all_depends'
from /usr/local/sbin/portupgrade:851:in
`get_uninstalled_depends'
from /usr/local/sbin/portupgrade:620:in `main'
from /usr/local/sbin/portupgrade:618:in `each'
 ... 9 levels...
from /usr/local/lib/ruby/1.8/optparse.rb:755:in `initialize'
from /usr/local/sbin/portupgrade:221:in `new'
from /usr/local/sbin/portupgrade:221:in `main'
from /usr/local/sbin/portupgrade:2168

-Kirill
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Whats this: UPDATING 2007030

2007-03-07 Thread Sergey Matveychuk
Kirill Ponomarew wrote:
 Hmm, it seems portupgrade-devel is broken eg:
 
 # portupgrade p5-Compress-Raw-Zlib-2.003
 [Gathering depends for archivers/p5-Compress-Raw-Zlib
 ./usr/local/sbin/portupgrade:842:in `get_all_depends': undefined
 method `compact' for #Set: {} (NoMethodError)

Yep. It was not tested well yet. But the message I've not seen yet. Thanks.

-- 
Dixi.
Sem.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Whats this: UPDATING 2007030

2007-03-07 Thread Kirill Ponomarew
On Thu, Mar 08, 2007 at 01:30:59AM +0300, Sergey Matveychuk wrote:
 Kirill Ponomarew wrote:
  Hmm, it seems portupgrade-devel is broken eg:
  
  # portupgrade p5-Compress-Raw-Zlib-2.003
  [Gathering depends for archivers/p5-Compress-Raw-Zlib
  ./usr/local/sbin/portupgrade:842:in `get_all_depends': undefined
  method `compact' for #Set: {} (NoMethodError)
 
 Yep. It was not tested well yet. But the message I've not seen yet. Thanks.

That's weird, because I'm getting this error if I portupgrade every
port I've installed.

-Kirill
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Zabbix

2007-03-07 Thread Edwin Groothuis
On Wed, Mar 07, 2007 at 08:50:10AM -0600, Michael Maynard wrote:
 I am writing to report a possible bug with the installation of zabbix
 from ports.  Is ucd-snmp required when net-snmp is already installed?
 There is no switch to install without ucd-snmp.

Can you run make config in /usr/ports/net-mgmt/php5-snmp and see
if you have enabled the old UCD-SNMP ?

Edwin

-- 
Edwin Groothuis  |Personal website: http://www.mavetju.org
[EMAIL PROTECTED]|  Weblog: http://weblog.barnet.com.au/edwin/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: fuzzyocr

2007-03-07 Thread Shaun Amott
On Tue, Mar 06, 2007 at 07:11:51PM -0800, Brian wrote:
 
 I've been using this awhile, and can't seem to figure out this error 
 which has been appearing since November 2006 at least.
 
 The log location is not right, it actually exists in 
 /usr/local/etc/mail/spamassassin/FuzzyOcr.log
 I could ln -s it but thats a bandaid, not a fix.
 
 I don't speak enough perl to make sense of the line number errors shown.
 
 /var/db/pkg shows p5-FuzzyOcr-2.3.b_2,1
 

The log file needs to be writable by the SpamAssassin process (although
it runs as root by default, if I recall). You can change the location in
FuzzyOcr.cf -- I probably ought to move it to /var/log by default.

-- 
Shaun Amott // PGP: 0x6B387A9A
A foolish consistency is the hobgoblin
of little minds. - Ralph Waldo Emerson
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Whats this: UPDATING 2007030

2007-03-07 Thread Heino Tiedemann
Kirill Ponomarew [EMAIL PROTECTED] wrote:

 On Wed, Mar 07, 2007 at 09:42:00PM +0300, Sergey Matveychuk wrote:
 Heino Tiedemann wrote:
  
  sorry I do not understand, WHAT to do there.
  
  Okay, there is an example, but what doas this mean concretely to me?
  
  Does that mean, that I am responsible fur all deps in ports? 
  That cannot be? is it?
  
 
 I think you can just ignore it if you don't understand. It's safe in the
 case. Do not run pkgdb -L. Dependencies will restore after a few upgrades.

 Hmm, it seems portupgrade-devel is broken eg:
^

The entry in UPDATING was about portupgrade-devel? Not portupgrade
normal

Heino

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


could anyone port VirtualBox to freebsd as host system?

2007-03-07 Thread lveax

hey all.

i noticed there is a vm called VirtualBox even faster then vmware..

and it is opensource.

is it possible that anyone one bring it to freebsd ports tree?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: fuzzyocr

2007-03-07 Thread Garrett Cooper

Shaun Amott wrote:

On Tue, Mar 06, 2007 at 07:11:51PM -0800, Brian wrote:
I've been using this awhile, and can't seem to figure out this error 
which has been appearing since November 2006 at least.


The log location is not right, it actually exists in 
/usr/local/etc/mail/spamassassin/FuzzyOcr.log

I could ln -s it but thats a bandaid, not a fix.

I don't speak enough perl to make sense of the line number errors shown.

/var/db/pkg shows p5-FuzzyOcr-2.3.b_2,1



The log file needs to be writable by the SpamAssassin process (although
it runs as root by default, if I recall). You can change the location in
FuzzyOcr.cf -- I probably ought to move it to /var/log by default.


Basically the file isn't readable / writable because of permissions 
issues, like Shaun said. All of the other 4 error messages are a 
biproduct of not being able to open up the file. Did you change the 
permissions by accident?

-Garrett
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: could anyone port VirtualBox to freebsd as host system?

2007-03-07 Thread Garrett Cooper

lveax wrote:

hey all.

i noticed there is a vm called VirtualBox even faster then vmware..

and it is opensource.

is it possible that anyone one bring it to freebsd ports tree?


Took a look at it and I'm interested. Just working on porting the 
configure file to FreeBSD / bourne sh.


-Garrett
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: fuzzyocr

2007-03-07 Thread Brian




Basically the file isn't readable / writable because of permissions 
issues, like Shaun said. All of the other 4 error messages are a 
biproduct of not being able to open up the file. Did you change the 
permissions by accident?

-Garrett
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

I do not jacking with this file.

-bash-2.05b$ cd /usr/local/etc/mail
-bash-2.05b$ ls -l
total 2
drwxr-xr-x  2 root  wheel  512 Mar  7 21:23 spamassassin
-bash-2.05b$ cd spamassassin/
-bash-2.05b$ ls -l
total 56
-rw-r--r--  1 root  wheel   5563 Mar  1 16:06 FuzzyOcr.cf
-rw-r--r--  1 root  wheel  0 Nov 27 14:45 FuzzyOcr.log
-r--r--r--  1 root  wheel  28236 Mar  7 21:23 FuzzyOcr.pm
-rw-r--r--  1 root  wheel415 Mar  1 16:06 FuzzyOcr.words
-rw-r--r--  1 root  wheel946 Oct 14 16:29 init.pre
-rw-r--r--  1 root  wheel949 Feb 26 16:18 init.pre.sample
-rw-r--r--  1 root  wheel   1221 Oct 14 16:28 local.cf
-rw-r--r--  1 root  wheel   1208 Feb 26 16:18 local.cf.sample
-rw-r--r--  1 root  wheel   2179 Feb 26 16:18 v310.pre
-rw-r--r--  1 root  wheel   2179 Feb 26 16:18 v310.pre.sample
-rw-r--r--  1 root  wheel806 Feb 26 16:18 v312.pre
-rw-r--r--  1 root  wheel806 Feb 26 16:18 v312.pre.sample


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


Snort fails to compile under 7-Current because ldd can't find -lpcre

2007-03-07 Thread Garrett Cooper

Here's a snippet of the build log.

configure:23477: result: no
configure:23494: checking for dlsym in -lc
configure:23524: cc -o conftest -O2 -pipe -fno-strict-aliasing -Wall 
-DDYNAMIC_PLUGIN  -I/usr/local/include -I  -L/usr/local/lib -lpcre -L 
conftest.c -lc  -lpcre -lpcap -lm  5

/usr/bin/ld: cannot find -lpcre
configure:23530: $? = 1
configure: failed program was:
| /* confdefs.h.  */
|
| #define PACKAGE_NAME 
| #define PACKAGE_TARNAME 
| #define PACKAGE_VERSION 
| #define PACKAGE_STRING 
| #define PACKAGE_BUGREPORT 
| #define PACKAGE snort
| #define VERSION 2.6.1.3
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_DLFCN_H 1
| #ifdef __cplusplus
| extern C void std::exit (int) throw (); using std::exit;
| #endif
| #define FREEBSD
| #define HAVE_STRINGS_H 1
| #define HAVE_STRING_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_SYS_SOCKIO_H 1
| #define HAVE_PATHS_H 1
| #define HAVE_SNPRINTF 1
| #define HAVE_STRLCPY 1
| #define HAVE_STRLCAT 1
| #define HAVE_STRERROR 1
| #define ERRLIST_PREDEFINED
| #define HAVE___FUNCTION__ 1
| #define HAVE_LIBM 1
| #define HAVE_LIBPCAP 1
| #define HAVE_PCRE_H 1
| #define HAVE_LIBPCRE 1
| /* end confdefs.h.  */
|
| /* Override any gcc2 internal prototype to avoid an error.  */
| #ifdef __cplusplus
| extern C
| #endif
| /* We use char because int might match the return type of a gcc2
|builtin and then its argument prototype would still apply.  */
| char dlsym ();
| int
| main ()
| {
| dlsym ();
|   ;
|   return 0;
| }

I was wondering if anyone knew what the next step would be to checking 
where gcc's trying to call up libraries from since I already have pcre 
installed.


Thanks!
-Garrett
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]