Zbigniew Szalbot wrote:
On Sun, 8 Oct 2006, Armin Pirkovitsch wrote:
Well another cvsup won't solve the problem since php hasn't been patched
yet. However if you're really sure you need and want this kind of port
installed just set the environment variable DISABLE_VULNERABILITIES.
However - y
Zbigniew Szalbot wrote:
> Hello,
>
> On Sun, 8 Oct 2006, Armin Pirkovitsch wrote:
>
>> Well another cvsup won't solve the problem since php hasn't been patched
>> yet. However if you're really sure you need and want this kind of port
>> installed just set the environment variable DISABLE_VULNERAB
Hello,
On Sun, 8 Oct 2006, Armin Pirkovitsch wrote:
Well another cvsup won't solve the problem since php hasn't been patched
yet. However if you're really sure you need and want this kind of port
installed just set the environment variable DISABLE_VULNERABILITIES.
However - you should be aware
Zbigniew Szalbot wrote:
> Hello,
>
> On Sun, 8 Oct 2006, Armin Pirkovitsch wrote:
>
>> run portaudit -F
>> it will update your database.
>> btw. just a sidenote - if you have not done it - after a cvsup of the
>> portstree you should also update your index (dependencies etc) by
>> running make in
Hello,
On Sun, 8 Oct 2006, Armin Pirkovitsch wrote:
run portaudit -F
it will update your database.
btw. just a sidenote - if you have not done it - after a cvsup of the
portstree you should also update your index (dependencies etc) by
running make index (takes long) or make fetchindex (fast) in
Zbigniew Szalbot wrote:
Hello,
On Sun, 8 Oct 2006, Erik Norgaard wrote:
I just csup'ed my ports tree and ran make on python without any problem.
portupgrade is a convenient tool but sometimes it fail for whatever reason,
no idea in your case.
I tried make as you suggest and:
$ sudo make
=
On Sunday 08 October 2006 22:21, Zbigniew Szalbot wrote:
> Hello,
>
> On Sun, 8 Oct 2006, Erik Norgaard wrote:
> > I just csup'ed my ports tree and ran make on python without any problem.
> >
> > portupgrade is a convenient tool but sometimes it fail for whatever
> > reason, no idea in your case.
>
Zbigniew Szalbot wrote:
> Hello,
>
> On Sun, 8 Oct 2006, Erik Norgaard wrote:
>
>> I just csup'ed my ports tree and ran make on python without any problem.
>>
>> portupgrade is a convenient tool but sometimes it fail for whatever
>> reason, no idea in your case.
>
> I tried make as you suggest a
Hello,
On Sun, 8 Oct 2006, Erik Norgaard wrote:
I just csup'ed my ports tree and ran make on python without any problem.
portupgrade is a convenient tool but sometimes it fail for whatever reason,
no idea in your case.
I tried make as you suggest and:
$ sudo make
===> python-2.4.3_1 has k
Zbigniew Szalbot wrote:
I am relatively new to FreeBSD. I use FreeBSD 6.1 stable release. I have
enabled portaudit and as a result now get reports about known
vulnarabilities. The problem I have encountered is this. I am trying to
update php and python and do it by first refreshing the ports t
Hello,
I am relatively new to FreeBSD. I use FreeBSD 6.1 stable release. I have
enabled portaudit and as a result now get reports about known
vulnarabilities. The problem I have encountered is this. I am trying to
update php and python and do it by first refreshing the ports tree by
using cvs
> You need both. cvsup(1) will synchronise the ports tree with the
> latest version -- that's all the Makefiles and stuff that are used to
> build ports, not the actual ports themselves. portupgrade(1) uses the
> files downloaded by cvsup(1) to build and install ports or to update
> any previous
On Sun, Jan 25, 2004 at 02:14:08AM -0800, Vanh wrote:
> I'm a FreeBSD newbie. Just got it installed last weekend. I have read
> the FreeBSD handbook, but still have some question. What is the
> different between cvsup and portupgrade? Do I need to use both? If not,
> which on
On Sunday 25 January 2004 02:14 am, Vanh wrote:
> Hi all,
>
> I'm a FreeBSD newbie. Just got it installed last weekend. I have read
> the FreeBSD handbook, but still have some question. What is the
> different between cvsup and portupgrade? Do I need to use both? If
> n
Hi all,
I'm a FreeBSD newbie. Just got it installed last weekend. I have read
the FreeBSD handbook, but still have some question. What is the
different between cvsup and portupgrade? Do I need to use both? If not,
which one is better?
Vanh
___
[
On Wed, Oct 08, 2003 at 11:33:25AM -0700, David Bear wrote:
>
> I'm still trying to muddle through the loads of different ways to keep
In addition to the other good advice given in this thread - when you get
used to portupgrade remember to edit /usr/local/etc/pkgtools.conf.
This file allows you to
On Wednesday 08 October 2003 02:01 pm, Kai Grossjohann wrote:
> Kent Stewart <[EMAIL PROTECTED]> writes:
> > make index
> > portsdb -u
>
> The docs for portsdb mention "portsdb -uU" (or was it "-Uu"?). Is
> there a difference between "portsdb -U" and "make index"? What's
> that difference?
Kris
Kent Stewart <[EMAIL PROTECTED]> writes:
> make index
> portsdb -u
The docs for portsdb mention "portsdb -uU" (or was it "-Uu"?). Is
there a difference between "portsdb -U" and "make index"? What's
that difference?
Kai
___
[EMAIL PROTECTED] mailing
On Wednesday 08 October 2003 11:33 am, David Bear wrote:
> I'm still trying to muddle through the loads of different ways to
> keep FreeBSD 'current' -- meaning, safely patched, aka RELENG_5_1
> (for me)
>
> As I conceptualize the operations there are two levels of 'patching',
> 1) the kernel and b
s-- and how well it plays with
cvsupdate.
The other rotten thing here is that cvsupdate requires modula-3 -- and
portupgrade requires ruby... It would really be nice if all this were
done in the most perfect language, python;-)
looking for some advice.. thx.
cvsup and portupgrade do different
On Wednesday 08 October 2003 01:33 pm, David Bear wrote:
> I'm still trying to muddle through the loads of different ways to keep
> FreeBSD 'current' -- meaning, safely patched, aka RELENG_5_1 (for me)
>
> As I conceptualize the operations there are two levels of 'patching',
> 1) the kernel and bas
On Wed, 08 Oct 2003 11:33:25 -0700, David Bear wrote:
> Seems there really should be a
> cleaner way to keep things updated.
There is.
> I've heard reference to a portupgrade package, but can't find any
> details on how and what it really does-- and how well it plays with
> cvsupdate.
portupg
I'm still trying to muddle through the loads of different ways to keep
FreeBSD 'current' -- meaning, safely patched, aka RELENG_5_1 (for me)
As I conceptualize the operations there are two levels of 'patching',
1) the kernel and base system
2) then all the ports that I may have installed
I've r
upgrade my ports with cvsup and portupgrade.
--
_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/
_/ _/
_/ Gary Dunn _/
_/ Open Slate Project _/
_/ http
24 matches
Mail list logo
