mm_cfg.py entry formating question

2007-04-18 Thread David Southwell 
Could anyone please tell me the correct format for multiple add_virtualhost 
entries in mm_cfg.py

Single is shown as:

add_virtualhost('virtualURL', 'virtualmailserver')

An example for multiples entries where more than one entry 
line is required (prefer one url and mailserver pair per line).

Thanks in advance



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

FreeBSD Port: openacs-5.3.0_1

2007-04-18 Thread aernout schmidt 

Dear Martin,

I have installed the openacs port with "make install", successfully I 
think. However, when I try the "install.sh" script it won't work. There 
are some older threads on the port in the OpenACS discussion list - 
mainly by Aldert Nooitgedacht - but these do not really help. Looking at 
the install script, it seems possible to specify quite a set of 
parameters, but there does not seem a simple setup/install howto  
available, helping out those, that do not immediately onderstand the 
ways  in which the port uses directories and the chown/chmod 
combinations required. When I experiment myself, I get stopped by 
"access denied" medssages on /usr/local/openacs/log/error.log. Can you 
give me a hint? Thanks in advance, Aernout Schmidt

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

umass device produces errors /var/log/messages

2007-04-18 Thread David Southwell 
Some help would be appreciated:

[EMAIL PROTECTED] /var/run]# camcontrol devlist
   at scbus0 target 0 lun 0 (pass0,da0)
   at scbus0 target 0 lun 1 (pass1,da1)
---
From /var/log/messages:
Apr 18 03:27:03 dns1 kernel: Opened disk da1 -> 6
Apr 18 03:27:05 dns1 kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 
0 0 0 0 0 0 0 0 
Apr 18 03:27:05 dns1 kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI Status 
Error
Apr 18 03:27:05 dns1 kernel: (da0:umass-sim0:0:0:0): SCSI Status: Check 
Condition
Apr 18 03:27:05 dns1 kernel: (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
Apr 18 03:27:05 dns1 kernel: (da0:umass-sim0:0:0:0): Medium not present
Apr 18 03:27:05 dns1 kernel: (da0:umass-sim0:0:0:0): Unretryable error
Apr 18 03:27:05 dns1 kernel: Opened disk da0 -> 6
Apr 18 03:27:05 dns1 kernel: (da1:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 
0 0 0 0 0 0 0 0 
Apr 18 03:27:05 dns1 kernel: (da1:umass-sim0:0:0:1): CAM Status: SCSI Status 
Error
Apr 18 03:27:05 dns1 kernel: (da1:umass-sim0:0:0:1): SCSI Status: Check 
Condition
Apr 18 03:27:05 dns1 kernel: (da1:umass-sim0:0:0:1): NOT READY asc:3a,0
Apr 18 03:27:05 dns1 kernel: (da1:umass-sim0:0:0:1): Medium not present
Apr 18 03:27:05 dns1 kernel: (da1:umass-sim0:0:0:1): Unretryable error
Apr 18 03:27:05 dns1 kernel: Opened disk da1 -> 6

Would anyone be kind enought to tell me how I stop the repeated error messages 
and have the device set-up to use?

Thanks in advance

Thanks in advance

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

Re: umass device produces errors /var/log/messages -IGNORE THIS THREAD

2007-04-18 Thread David Southwell 

Sorry posted to wrong list -- this is for questions!!

On Wednesday 18 April 2007 03:32:10 David Southwell wrote:
> Some help would be appreciated:
>
> [EMAIL PROTECTED] /var/run]# camcontrol devlist
>at scbus0 target 0 lun 0 (pass0,da0)
>at scbus0 target 0 lun 1 (pass1,da1)
> ---
> From /var/log/messages:
> Apr 18 03:27:03 dns1 kernel: Opened disk da1 -> 6
> Apr 18 03:27:05 dns1 kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25
> 0 0 0 0 0 0 0 0 0
> Apr 18 03:27:05 dns1 kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI
> Status Error
> Apr 18 03:27:05 dns1 kernel: (da0:umass-sim0:0:0:0): SCSI Status: Check
> Condition
> Apr 18 03:27:05 dns1 kernel: (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
> Apr 18 03:27:05 dns1 kernel: (da0:umass-sim0:0:0:0): Medium not present
> Apr 18 03:27:05 dns1 kernel: (da0:umass-sim0:0:0:0): Unretryable error
> Apr 18 03:27:05 dns1 kernel: Opened disk da0 -> 6
> Apr 18 03:27:05 dns1 kernel: (da1:umass-sim0:0:0:1): READ CAPACITY. CDB: 25
> 20 0 0 0 0 0 0 0 0
> Apr 18 03:27:05 dns1 kernel: (da1:umass-sim0:0:0:1): CAM Status: SCSI
> Status Error
> Apr 18 03:27:05 dns1 kernel: (da1:umass-sim0:0:0:1): SCSI Status: Check
> Condition
> Apr 18 03:27:05 dns1 kernel: (da1:umass-sim0:0:0:1): NOT READY asc:3a,0
> Apr 18 03:27:05 dns1 kernel: (da1:umass-sim0:0:0:1): Medium not present
> Apr 18 03:27:05 dns1 kernel: (da1:umass-sim0:0:0:1): Unretryable error
> Apr 18 03:27:05 dns1 kernel: Opened disk da1 -> 6
>
> Would anyone be kind enought to tell me how I stop the repeated error
> messages and have the device set-up to use?
>
> Thanks in advance
>
> Thanks in advance
>
> David
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"


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

This mailaccount is no longer active

2007-04-18 Thread joerg_wunsch 
Effective December 31, 2006, I am no longer an employee of interface
systems GmbH.  Please direct any business mails to

or call +49-351-31809-44.

If you want to contact me privately, please send an email to

Your mail will be forwarded.


Zum 31. Dezember 2006 endet mein Anstellungsverhaeltnis bei interface
systems GmbH.  Bitte richten Sie alle dienstlichen emails an

oder rufen Sie an unter +49-351-31809-44.

Falls Sie mich privat erreichen wollen, senden Sie bitte eine email an

Ihre Mail wird weitergeleitet.

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

Re: [wine] can't run /libexec/ld-elf.so.1 not found

2007-04-18 Thread Norikatsu Shigemura 
On Tue, 17 Apr 2007 22:53:57 +0200
regisr <[EMAIL PROTECTED]> wrote:
> > It's well-known problem.  The maximum hard-limit data size
> > (kern.maxdsiz) is too big (over about 1GB).  So you may set
> > kern.maxdsiz=805306368 to your /boot/loader.conf.
> Ok I find the following PR:
> http://www.freebsd.org/cgi/query-pr.cgi?pr=94413
> May be this info should be added in the pkg-message.

I think so.  Hi gerald, how about?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: mm_cfg.py entry formating question

2007-04-18 Thread Jeffrey Goldberg 


On Apr 18, 2007, at 3:20 AM, David Southwell wrote:

Could anyone please tell me the correct format for multiple  
add_virtualhost

entries in mm_cfg.py

Single is shown as:

add_virtualhost('virtualURL', 'virtualmailserver')

An example for multiples entries where more than one entry
line is required (prefer one url and mailserver pair per line).


add_virtualhost('vhostURL1', 'vhostmailserver1')
add_virtualhost('vhostURL2', 'vhostmailserver2')
add_virtualhost('vhostURL3', 'vhostmailserver3')
add_virtualhost('vhostURL4', 'vhostmailserver4')

vhostURL[1-4] must all be unique, but vhostmailserver[1-4] may  
overlap with each other.


-j


--
Jeffrey Goldberghttp://www.goldmark.org/jeff/

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

Re: Utility for safe updating of ports in base system

2007-04-18 Thread RW 
On Tue, 17 Apr 2007 20:43:51 -0700
Garrett Cooper <[EMAIL PROTECTED]> wrote:

> RW wrote:
> > On Tue, 17 Apr 2007 14:31:39 -0400
> > Adam Stroud <[EMAIL PROTECTED]> wrote:
> > 
> > 
> >> I was just on the FreeBSD "list of projects and ideas fot
> >> volunteers" page and I was wondering if anyone was working on the
> >> "portupgrade in C" utility.  I would be willing to help
> >> (code/document/test) if it's needed.
> > 
> > What would be the point of putting any port-upgrading tool in the
> > base-system? The ports tree isn't branched, so why branch such
> > tools in the base-system. IMO they logically belong in ports where
> > they are better able to follow any developments in the
> > ports-system. 
> 
> I'm working on combining the pkg_* tools along with the existing 
> makefile system with a bourne shell file for my SoC project(*)
> 
> As for writing a utility in C, why? Almost everything's there right
> now and just needs to be strung together with some clever scripting
> to make it all work. C in this case is just overkill IMO.
> 
> I'm sorry RW, because while I do agree to some extent, there should
> be something out of the box that works with the Makefiles and does 
> everything necessary to install ports, apart from someone manually
> going to each directory and typing in "make install", or using some
> "advanced" functionality in the Makefiles.

You "make install"  (or pkg_add) once to build your preferred tool.
If that's too much trouble, sysinstall might add the package as part of
a standard profile - it does this with xorg. Or it could add the
package when it asks you if you want the ports tree. This is not a
serious argument for putting something in the base-system. 

If you put a build tool in the base-system then sooner or later someone
will need a newer version, which means having a port too and flags to
say which is the preferred version. This will lead to needless
confusion. And since few people will want to upgrade their up-to-date
ports with an out-of-date tool, I suspect that most people will go for
the ports version anyway.

I've yet to hear a single cogent argument for this. 

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

Re: mm_cfg.py entry formating question

2007-04-18 Thread David Southwell 
On Wednesday 18 April 2007 06:48:01 Jeffrey Goldberg wrote:
> On Apr 18, 2007, at 3:20 AM, David Southwell wrote:
> > Could anyone please tell me the correct format for multiple
> > add_virtualhost
> > entries in mm_cfg.py
> >
> > Single is shown as:
> >
> > add_virtualhost('virtualURL', 'virtualmailserver')
> >
> > An example for multiples entries where more than one entry
> > line is required (prefer one url and mailserver pair per line).
>
> add_virtualhost('vhostURL1', 'vhostmailserver1')
> add_virtualhost('vhostURL2', 'vhostmailserver2')
> add_virtualhost('vhostURL3', 'vhostmailserver3')
> add_virtualhost('vhostURL4', 'vhostmailserver4')
>
> vhostURL[1-4] must all be unique, but vhostmailserver[1-4] may
> overlap with each other.
>
> -j

Thank you 
I have found that different elements in the config files seem to have their 
own rules for multiples.. I would be helpful if they had examples of multiple 
entries as well as singles.

Thanks again
David

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

Re: Utility for safe updating of ports in base system

2007-04-18 Thread Adam Stroud 
Garrett Cooper  u.washington.edu> writes:

> I'm working on combining the pkg_* tools along with the existing 
> makefile system with a bourne shell file for my SoC project(*)
> 
> As for writing a utility in C, why? Almost everything's there right now 
> and just needs to be strung together with some clever scripting to make 
> it all work. C in this case is just overkill IMO.
> 
> I'm sorry RW, because while I do agree to some extent, there should be 
> something out of the box that works with the Makefiles and does 
> everything necessary to install ports, apart from someone manually going 
> to each directory and typing in "make install", or using some "advanced" 
> functionality in the Makefiles.
> 
> (*) This is the 2nd goal on my list out of 3 items, so it's going to be 
> a while before I get to it (I estimate 2 months).
> 
> -Garrett


I was not suggesting writing the utilities in C, I was just indicating the the
topic on the FreeBSD "ideas" page.  Frankly, I am a "best tool for the job" type
of guy.  My intent was just to probe the community and see if anything was being
developed and if anyone needed any help.

Adam

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

Lynx -vulnerabilities- is this permanent?

2007-04-18 Thread David Southwell 
Hi

portupgrade -a produces following output for lynx on cvsup from today.
freebsd 6.1
-
--->  Upgrading 'lynx-2.8.5_2' to 'lynx-2.8.6_4' (www/lynx)
--->  Building '/usr/ports/www/lynx'
===>  Cleaning for lynx-2.8.6_4
===>  lynx-2.8.6_4 has known vulnerabilities:
=> lynx -- remote buffer overflow.
   Reference: 

=> Please update your ports tree and try again.
*** Error code 1

Stop in /usr/ports/www/lynx.

Any news or advice forthcoming?

david

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

Re: Lynx -vulnerabilities- is this permanent?

2007-04-18 Thread Lowell Gilbert 
David Southwell <[EMAIL PROTECTED]> writes:

> portupgrade -a produces following output for lynx on cvsup from today.
> freebsd 6.1
> -
> --->  Upgrading 'lynx-2.8.5_2' to 'lynx-2.8.6_4' (www/lynx)
> --->  Building '/usr/ports/www/lynx'
> ===>  Cleaning for lynx-2.8.6_4
> ===>  lynx-2.8.6_4 has known vulnerabilities:
> => lynx -- remote buffer overflow.
>Reference: 
> 
> => Please update your ports tree and try again.
> *** Error code 1
>
> Stop in /usr/ports/www/lynx.
>
> Any news or advice forthcoming?

That doesn't *seem* to be applicable to the current version.
It looks like a version-number parsing problem producing a false warning.
I don't have access to my build machine to check more closely, though...
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Lynx -vulnerabilities- is this permanent?

2007-04-18 Thread [LoN]Kamikaze 
David Southwell wrote:
> Hi
> 
> portupgrade -a produces following output for lynx on cvsup from today.
> freebsd 6.1
> -
> --->  Upgrading 'lynx-2.8.5_2' to 'lynx-2.8.6_4' (www/lynx)
> --->  Building '/usr/ports/www/lynx'
> ===>  Cleaning for lynx-2.8.6_4
> ===>  lynx-2.8.6_4 has known vulnerabilities:
> => lynx -- remote buffer overflow.
>Reference: 
> 
> => Please update your ports tree and try again.
> *** Error code 1
> 
> Stop in /usr/ports/www/lynx.
> 
> Any news or advice forthcoming?
> 
> david

Did you try a 'portaudit -F'?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Tracking port and package flags/options

2007-04-18 Thread Ulrich Spoerlein 
James E. Flemer wrote:
> There are also two other unrelated tweaks to the ports infrastructure in the 
> patch, but I've 
> included them as I've been using them for a long time as well.  First is to 
> make backups when 
> using USE_DOS2UNIX.  Second is to change dependency tracking to first-order 
> only (versus 
> recursive); see http://docs.freebsd.org/cgi/mid.cgi?427E4687.40901 for 
> previous discussion.

I would favour the first-order only approach, but often it is not so
clearly cut. All those WITH_ flags make the matter even worse.

I finished building OOo with my parallel package build script, and as
you can see from the attached patch, the dependency information is
rather excessive. (I'm working on minimizing the graph, though)

Ulrich Spoerlein
-- 
"The trouble with the dictionary is you have to know how the word is
spelled before you can look it up to see how it is spelled."
-- Will Cuppy
digraph pkg {
 rankdir=BT;
  n0 [ label="perl-5.8.8\n292.67s" ];
  n1 [ label="unzip-5.52_3\n9.13s" ];
  n2 [ label="m4-1.4.8_1\n19.54s" ];
  n3 [ label="zip-2.32\n7.03s" ];
  n4 [ label="libtool-1.5.22_4\n14.55s" ];
  n5 [ label="libiconv-1.9.2_2\n33.56s" ]; n5 -> n4;
  n6 [ label="gettext-0.16.1_1\n178.38s" ]; n6 -> n4; n6 -> n5;
  n7 [ label="gmake-3.81_1\n21.82s" ]; n7 -> n6;
  n8 [ label="imake-6.9.0_1\n45.13s" ]; n8 -> n0;
  n9 [ label="libdrm-2.0.2\n7.21s" ];
  n10 [ label="pkg-config-0.21\n41.00s" ]; n10 -> n7;
  n11 [ label="freetype2-2.2.1_1\n52.61s" ]; n11 -> n7; n11 -> n4; n11 -> n10;
  n12 [ label="expat-2.0.0_1\n16.67s" ];
  n13 [ label="fontconfig-2.4.2,1\n37.70s" ]; n13 -> n4; n13 -> n7; n13 -> n10; 
n13 -> n11; n13 -> n12;
  n14 [ label="xorg-libraries-6.9.0_1\ns" ]; n14 -> n8; n14 -> n9; n14 -> n11; 
n14 -> n13;
  n15 [ label="open-motif-2.2.3_2\n302.37s" ]; n15 -> n7; n15 -> n4; n15 -> 
n14; n15 -> n8;
  n16 [ label="autoconf-2.13.000227_5\n21.23s" ]; n16 -> n0; n16 -> n2;
  n17 [ label="automake-1.4.6_2\n19.14s" ]; n17 -> n0; n17 -> n16;
  n18 [ label="popt-1.7_3\n15.39s" ]; n18 -> n4; n18 -> n6;
  n19 [ label="rpm-3.0.6_13\n84.50s" ]; n19 -> n7; n19 -> n17; n19 -> n16; n19 
-> n4; n19 -> n18; n19 -> n6;
  n20 [ label="linux_base-fc-4_9\n102.80s" ]; n20 -> n19;
  n21 [ label="javavmwrapper-2.3\n.74s" ];
  n22 [ label="linux-expat-1.95.8\n34.60s" ]; n22 -> n19; n22 -> n20;
  n23 [ label="linux-fontconfig-2.2.3_6\n60.53s" ]; n23 -> n19; n23 -> n22; n23 
-> n20;
  n24 [ label="linux-xorg-libs-6.8.2_5\n65.99s" ]; n24 -> n19; n24 -> n23; n24 
-> n20;
  n25 [ label="linux-sun-jdk-1.4.2.13\n100.09s" ]; n25 -> n20; n25 -> n21; n25 
-> n24;
  n26 [ label="glib-2.12.11\n121.19s" ]; n26 -> n0; n26 -> n4; n26 -> n7; n26 
-> n10; n26 -> n6;
  n27 [ label="desktop-file-utils-0.12\n31.26s" ]; n27 -> n10; n27 -> n18; n27 
-> n26;
  n28 [ label="nspr-4.6.6\n21.65s" ]; n28 -> n7;
  n29 [ label="jdk-1.5.0p4_1\n7581.87s" ]; n29 -> n1; n29 -> n2; n29 -> n3; n29 
-> n15; n29 -> n25; n29 -> n7; n29 -> n10; n29 -> n27; n29 -> n28; n29 -> n5; 
n29 -> n26; n29 -> n21;
  n30 [ label="bison-1.75_2,1\n23.85s" ]; n30 -> n2; n30 -> n6;
  n31 [ label="gcc-ooo-3.4.1_2\n871.28s" ]; n31 -> n0; n31 -> n7; n31 -> n30;
  n32 [ label="coreutils-6.7\n115.58s" ]; n32 -> n7; n32 -> n6;
  n33 [ label="patch-2.5.4\n6.23s" ];
  n34 [ label="p5-Compress-Raw-Zlib-2.004\n19.82s" ]; n34 -> n0;
  n35 [ label="p5-IO-Compress-Base-2.004\n18.27s" ]; n35 -> n0;
  n36 [ label="p5-IO-Compress-Zlib-2.004\n19.92s" ]; n36 -> n0; n36 -> n34; n36 
-> n35;
  n37 [ label="p5-Compress-Zlib-2.004\n18.80s" ]; n37 -> n0; n37 -> n34; n37 -> 
n36;
  n38 [ label="p5-Scalar-List-Utils-1.19,1\n19.20s" ]; n38 -> n0;
  n39 [ label="p5-PathTools-3.24\n18.95s" ]; n39 -> n0; n39 -> n38;
  n40 [ label="p5-File-Temp-0.18\n19.42s" ]; n40 -> n0;
  n41 [ label="p5-File-Which-0.05\n17.94s" ]; n41 -> n0;
  n42 [ label="p5-Archive-Zip-1.18\n21.27s" ]; n42 -> n0; n42 -> n37; n42 -> 
n39; n42 -> n40; n42 -> n41;
  n43 [ label="bison-2.3\n29.46s" ]; n43 -> n2; n43 -> n6;
  n44 [ label="apache-ant-1.7.0\n101.28s" ]; n44 -> n21; n44 -> n29;
  n45 [ label="p5-XML-Parser-2.34_2\n22.61s" ]; n45 -> n0; n45 -> n12;
  n46 [ label="intltool-0.35.5_2\n23.68s" ]; n46 -> n0; n46 -> n45; n46 -> n7; 
n46 -> n5;
  n47 [ label="gnomehier-2.2\n7.79s" ]; n47 -> n14;
  n48 [ label="gnome-mime-data-2.18.0\n36.83s" ]; n48 -> n7; n48 -> n46; n48 -> 
n10; n48 -> n6; n48 -> n47;
  n49 [ label="libart_lgpl-2.3.19,1\n20.24s" ]; n49 -> n4; n49 -> n10;
  n50 [ label="jpeg-6b_4\n28.69s" ]; n50 -> n4;
  n51 [ label="png-1.2.14\n13.46s" ];
  n52 [ label="tiff-3.8.2_1\n56.62s" ]; n52 -> n4; n52 -> n50;
  n53 [ label="libgpg-error-1.4_1\n18.18s" ]; n53 -> n4; n53 -> n5; n53 -> n6;
  n54 [ label="libgcrypt-1.2.4_1\n55.64s" ]; n54 -> n4; n54 -> n53;
  n55 [ label="libtasn1-0.3.9\n19.06s" ]; n55 -> n10;
  n56 [ label="gnutls-1.6.1_2\n146.02s" ]; n56 -> n10; n56 -> n54; n56 -> n53; 
n56 -> n55; n56 -> n5; n56 -> n6;
  n57 [ label="cups-base-1.2.10\ns" ]; n57 -> n7; n57 -> n50; n57 -> n51; n57 
-> n52; n57 -> n56

Re: FreeMat 3.0 doesn't call functions and help

2007-04-18 Thread Vittorio De Martino 
Il Sunday 15 April 2007 22:11:12 Thierry Thomas ha scritto:
> Le Lun  9 avr 07 à 16:39:49 +0200, Vittorio De Martino
> <[EMAIL PROTECTED]>
>
>  écrivait :
> > P.S. By the way, launching FreeMat as root the "Help on line" works
> > whilst inv still doesn't work. Ciao Vittorio
>
> Hello,
>
> I have just upgraded FreeMAT to 3.1, which fixes the inv() problem, and
> which should fix this "Help on line" bug too; could you please check it?
>

Yes, with the new version 3.1 inv now works fine. Unfortunately the "Help on 
line" still doesn't work. I think that something worsened because with this 
new port now I cannot use the help on line even as root (in the previous 
version "Help online" as root worked quite well).

Ciao
Vittorio 

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

Re: Lynx -vulnerabilities- is this permanent?

2007-04-18 Thread Jeffrey Goldberg 

On Apr 18, 2007, at 1:42 PM, [LoN]Kamikaze wrote:


David Southwell wrote:

Hi

portupgrade -a produces following output for lynx on cvsup from  
today.

freebsd 6.1
-
--->  Upgrading 'lynx-2.8.5_2' to 'lynx-2.8.6_4' (www/lynx)
--->  Building '/usr/ports/www/lynx'
===>  Cleaning for lynx-2.8.6_4
===>  lynx-2.8.6_4 has known vulnerabilities:
=> lynx -- remote buffer overflow.
   Reference:


=> Please update your ports tree and try again.
*** Error code 1

Stop in /usr/ports/www/lynx.

Any news or advice forthcoming?

david


Did you try a 'portaudit -F'?


I'm having the same problem as David, though I'm on 6.2.  Running

  portaudit -F

made no difference for  me.

-j

--
Jeffrey Goldberghttp://www.goldmark.org/jeff/

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

Re: Lynx -vulnerabilities- is this permanent?

2007-04-18 Thread Foxfair Hu 
Lowell Gilbert wrote:
> David Southwell <[EMAIL PROTECTED]> writes:
> 
>> portupgrade -a produces following output for lynx on cvsup from today.
>> freebsd 6.1
>> -
>> --->  Upgrading 'lynx-2.8.5_2' to 'lynx-2.8.6_4' (www/lynx)
>> --->  Building '/usr/ports/www/lynx'
>> ===>  Cleaning for lynx-2.8.6_4
>> ===>  lynx-2.8.6_4 has known vulnerabilities:
>> => lynx -- remote buffer overflow.
>>Reference: 
>> 
>> => Please update your ports tree and try again.
>> *** Error code 1
>>
>> Stop in /usr/ports/www/lynx.
>>
>> Any news or advice forthcoming?
> 
> That doesn't *seem* to be applicable to the current version.
> It looks like a version-number parsing problem producing a false warning.
> I don't have access to my build machine to check more closely, though...
> 
> .
> 

Definitely a false alert, lynx 2.8.5rel4 had fixed the problem, and it
was rev1.112 of Makefile
in www/lynx. If no one objects, I'll put this diff to prevent portaudit
send wrong warning again:


--- /usr/ports/www/lynx/MakefileMon Apr 16 00:04:47 2007
+++ ./Makefile  Thu Apr 19 10:06:59 2007
@@ -7,11 +7,11 @@
 
 PORTNAME=  lynx
 PORTVERSION=   2.8.6
-PORTREVISION=  4
+PORTREVISION=  5
 CATEGORIES=www ipv6
 MASTER_SITES=  http://lynx.isc.org/current/ \
ftp://lynx.isc.org/lynx${PORTVERSION}/patches/:patches
-DISTNAME=  ${PORTNAME}${PORTVERSION}rel.${PORTREVISION}
+DISTNAME=  ${PORTNAME}${PORTVERSION}rel.4
 
 MAINTAINER?=   [EMAIL PROTECTED]
 COMMENT?=  A non-graphical, text-based World-Wide Web client
@@ -28,6 +28,9 @@
 .if defined(ENABLE_DEFAULT_COLORS)
 CONFIGURE_ARGS+=--enable-default-colors
 .endif
+
+# CVE-2005-3120 was fixed in lynx 2.8.5rel4
+DISABLE_VULNERABILITIES=   YES
 
 MAKE_ARGS= helpdir=${L_HELP} docdir=${DOCSDIR}
 MAKEFILE=  makefile
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Lynx -vulnerabilities- is this permanent?

2007-04-18 Thread Kris Kennaway 
On Thu, Apr 19, 2007 at 10:10:41AM +0800, Foxfair Hu wrote:
> Lowell Gilbert wrote:
> > David Southwell <[EMAIL PROTECTED]> writes:
> > 
> >> portupgrade -a produces following output for lynx on cvsup from today.
> >> freebsd 6.1
> >> -
> >> --->  Upgrading 'lynx-2.8.5_2' to 'lynx-2.8.6_4' (www/lynx)
> >> --->  Building '/usr/ports/www/lynx'
> >> ===>  Cleaning for lynx-2.8.6_4
> >> ===>  lynx-2.8.6_4 has known vulnerabilities:
> >> => lynx -- remote buffer overflow.
> >>Reference: 
> >> 
> >> => Please update your ports tree and try again.
> >> *** Error code 1
> >>
> >> Stop in /usr/ports/www/lynx.
> >>
> >> Any news or advice forthcoming?
> > 
> > That doesn't *seem* to be applicable to the current version.
> > It looks like a version-number parsing problem producing a false warning.
> > I don't have access to my build machine to check more closely, though...
> > 
> > .
> > 
> 
> Definitely a false alert, lynx 2.8.5rel4 had fixed the problem, and it
> was rev1.112 of Makefile
> in www/lynx. If no one objects, I'll put this diff to prevent portaudit
> send wrong warning again:

Wrong fix, fix the vuxml instead of hacking around it.

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