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
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
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
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
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.
I tried
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
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)
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 index (takes
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:
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.
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 -
On Mon, 7 Jun 2004, [iso-8859-1] Stephen Liu wrote:
Hi folks,
I am still not very clear on the function between
# cvsup -g /usr/local/etc/cvsup/stable-supfile
and
# portupgrade -aRr
I have following questions;
1) What will be their diffenece in function
2) If having run
#
On Mon, Jun 07, 2004 at 01:34:33PM +0800, Stephen Liu said:
Hi folks,
I am still not very clear on the function between
# cvsup -g /usr/local/etc/cvsup/stable-supfile
and
# portupgrade -aRr
I have following questions;
1) What will be their diffenece in function
2) If having
Hi Remko,
Tks for your advice.
- snip -
2) If having run
# cvsup -g /usr/local/etc/cvsup/ports-supfile
# cvsup -g /usr/local/etc/cvsup/stable-supfile
Whether I still need to run
# portupgrade -aRr
Yes you can do this, since cvsup retrieve's the
latest sources for the
Hi Viktor,
Tks for your advice.
- snip -
# cvsup -g /usr/local/etc/cvsup/ports-supfile
# cvsup -g /usr/local/etc/cvsup/stable-supfile
Whether I still need to run
# portupgrade -aRr
3) If NO to 2) above
When shall I need to run
# portupgrade -aRr
4) Whether following
On Mon, Jun 07, 2004 at 05:13:14PM +0800, Stephen Liu wrote:
After running
# cvsup -g /usr/local/etc/cvsup/ports-supfile
# cvsup -g /usr/local/etc/cvsup/stable-supfile
before running
# portupgrade -aRr
whether I need to run
# pkgdb -F
You don't generally need to run this every time
Hi folks,
I am still not very clear on the function between
# cvsup -g /usr/local/etc/cvsup/stable-supfile
and
# portupgrade -aRr
I have following questions;
1) What will be their diffenece in function
2) If having run
# cvsup -g /usr/local/etc/cvsup/ports-supfile
# cvsup -g
Stephen,
Stephen Liu wrote:
Hi folks,
I am still not very clear on the function between
# cvsup -g /usr/local/etc/cvsup/stable-supfile
and
# portupgrade -aRr
I have following questions;
1) What will be their diffenece in function
2) If having run
# cvsup -g /usr/local/etc/cvsup/ports-supfile
#
Reading from the FreeBSD handbook on Using the Ports Collection leaves me a
bit confused wrt CVSup and portupgrade... do these utilities accomplish the
same thing?
Thanks,
Jay
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman
On Fri, Apr 02, 2004 at 07:27:31PM -0600, Jay Moore wrote:
Reading from the FreeBSD handbook on Using the Ports Collection leaves me a
bit confused wrt CVSup and portupgrade... do these utilities accomplish the
same thing?
No, cvsup updates the files that make up the ports collection
On Fri, Apr 02, 2004 at 07:27:31PM -0600, Jay Moore wrote:
Reading from the FreeBSD handbook on Using the Ports Collection leaves me a
bit confused wrt CVSup and portupgrade... do these utilities accomplish the
same thing?
Thanks,
Jay
On Friday 02 April 2004 07:32 pm, Kris Kennaway wrote:
Reading from the FreeBSD handbook on Using the Ports Collection leaves
me a bit confused wrt CVSup and portupgrade... do these utilities
accomplish the same thing?
No, cvsup updates the files that make up the ports collection
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 previously
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
___
[EMAIL
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
not, which one is better
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 one is better?
You need
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
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.
portupgrade
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 base
.
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 things.
Cvsup will keep your copy
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 base
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 list
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 has a script that
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
upgrade my ports with cvsup and portupgrade.
--
_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/
_/ _/
_/ Gary Dunn _/
_/ Open Slate Project _/
_/ http
35 matches
Mail list logo