Re: upgrading portupgrade

2008-07-02 Thread Kevin Monceaux

Zbigniew,

On Wed, 2 Jul 2008, Zbigniew Szalbot wrote:

In order to upgrade portupgrade, is it enough to run make, make install && 
make clean?


If you already have portupgrade installed and tried the above technique I 
think you'd get an error at the end of make install saying the port is 
already installed.  You'd need to use either make reinstall or make 
deinstall followed by make reinstall.  I've been using portupgrade so long 
I forget which.


I am not familiar with make but something tells me I won't be able to upgrade 
portupgrade by means of portupgrade ;)


I've never had any trouble upgrading portupgrade via portupgrade.  Boy, 
that's almost a tongue twister.  :-)


If there's a change to portupgrade that would require a special upgrade 
procedure, it will be noted in /usr/ports/UPDATING.  Earlier today I 
switched my home PC from portupgrade to portupgrade-devel to try out some 
new features just added to the devel version.  All that was involved was:


portupgrade -fo ports-mgmt/portupgrade-devel portupgrade




Kevin
http://www.RawFedDogs.net
http://www.WacoAgilityGroup.org
Bruceville, TX

Si hoc legere scis nimium eruditionis habes.
Longum iter est per praecepta, breve et efficax per exempla!!!

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


Re: upgrading portupgrade

2008-07-01 Thread Zbigniew Szalbot

Hi there,

I am not familiar with make but something tells me I won't be able to 
upgrade portupgrade by means of portupgrade ;)



Upgrading portupgrade via portupgrade has always worked for me.


Thanks a lot! I should have tried it before writing to the list. It 
worked very well indeed!


--
Zbigniew Szalbot
www.LCWords.com


smime.p7s
Description: S/MIME Cryptographic Signature


Re: upgrading portupgrade

2008-07-01 Thread Fraser Tweedale
On Wed, Jul 02, 2008 at 08:21:59AM +0200, Zbigniew Szalbot wrote:
> Hi there,
> 
> In order to upgrade portupgrade, is it enough to run make, make install 
> && make clean?
> 
> I am not familiar with make but something tells me I won't be able to 
> upgrade portupgrade by means of portupgrade ;)
> 
> Thanks!
> 
> -- 
> Zbigniew Szalbot
> www.LCWords.com

Upgrading portupgrade via portupgrade has always worked for me.

If you're paranoid though, you can always do:

cd /usr/ports/ports-mgmt/portupgrade
make && make deinstall && make reinstall

...which is the essence of what portupgrade does anyway, minus all the 
extra stuff ;)

frase


pgpNwhjmCzSaT.pgp
Description: PGP signature


upgrading portupgrade

2008-07-01 Thread Zbigniew Szalbot

Hi there,

In order to upgrade portupgrade, is it enough to run make, make install 
&& make clean?


I am not familiar with make but something tells me I won't be able to 
upgrade portupgrade by means of portupgrade ;)


Thanks!

--
Zbigniew Szalbot
www.LCWords.com


smime.p7s
Description: S/MIME Cryptographic Signature


Re: Errors after upgrading portupgrade

2006-01-02 Thread Jack Raats

Top gives:

last pid: 28570;  load averages:  0.00,  0.00,  0.00 
up 0+02:48:39  10:16:15

94 processes:  2 running, 92 sleeping
CPU states:  0.4% user,  0.0% nice,  0.7% system,  0.0% interrupt, 98.9% 
idle

Mem: 23M Active, 40M Inact, 76M Wired, 60K Cache, 60M Buf, 353M Free
Swap: 2048M Total, 88M Used, 1960M Free, 4% Inuse

I think memory is not the problem. The errors started after the portupgrade 
to version 2.0.0,1


Jack

- Original Message - 
From: "Scott Smith" <[EMAIL PROTECTED]>

To: "Jack Raats" <[EMAIL PROTECTED]>
Cc: 
Sent: Monday, January 02, 2006 9:36 AM
Subject: Re: Errors after upgrading portupgrade



-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

How's the machine's memory usage?

Scott

Jack Raats wrote:

Hi,

Running the new portupgrade 2.0.0,1 gives the following errors:

orac# portupgrade -Na
[Updating the portsdb  in /usr/ports ... - 13945 port 
entries found 
.1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000. 
. done]
** Package origin of 'bison' has been changed: 'devel/bison' -> 
'devel/bison2'
** No need to upgrade 'bison-1.75_2,1' (>= bison-2.1_1). (specify -f to 
force)
/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:89:in `<<': failed to 
allocate memory (NoMemoryError)

from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:89:in `trace'
from /usr/local/sbin/portupgrade:723:in `do_upgrade'
from /usr/local/sbin/portupgrade:696:in `main'
from /usr/local/sbin/portupgrade:693:in `each'
from /usr/local/sbin/portupgrade:693:in `main'
from /usr/local/sbin/portupgrade:208:in `initialize'
from /usr/local/sbin/portupgrade:208:in `new'
from /usr/local/sbin/portupgrade:208:in `main'
from /usr/local/sbin/portupgrade:1893

Anyone know how to cure this error?

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


- --
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (MingW32)

iD8DBQFDuOYnKBeC2yZ3EEsRAkItAJ9y7sj6op+L8fFH8VBMNaA5Bu0FeQCfSzPE
fz/v1M46YNomG72SmNGTSxE=
=1N4B
-END PGP SIGNATURE-



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


Re: Errors after upgrading portupgrade

2006-01-02 Thread Scott Smith
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

How's the machine's memory usage?

Scott

Jack Raats wrote:
> Hi,
> 
> Running the new portupgrade 2.0.0,1 gives the following errors:
> 
> orac# portupgrade -Na
> [Updating the portsdb  in /usr/ports ... - 13945 port 
> entries found 
> .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.
>  . done]
> ** Package origin of 'bison' has been changed: 'devel/bison' -> 'devel/bison2'
> ** No need to upgrade 'bison-1.75_2,1' (>= bison-2.1_1). (specify -f to force)
> /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:89:in `<<': failed to allocate 
> memory (NoMemoryError)
> from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:89:in `trace'
> from /usr/local/sbin/portupgrade:723:in `do_upgrade'
> from /usr/local/sbin/portupgrade:696:in `main'
> from /usr/local/sbin/portupgrade:693:in `each'
> from /usr/local/sbin/portupgrade:693:in `main'
> from /usr/local/sbin/portupgrade:208:in `initialize'
> from /usr/local/sbin/portupgrade:208:in `new'
> from /usr/local/sbin/portupgrade:208:in `main'
> from /usr/local/sbin/portupgrade:1893
> 
> Anyone know how to cure this error?
> 
> Jack
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"

- --
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (MingW32)

iD8DBQFDuOYnKBeC2yZ3EEsRAkItAJ9y7sj6op+L8fFH8VBMNaA5Bu0FeQCfSzPE
fz/v1M46YNomG72SmNGTSxE=
=1N4B
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Errors after upgrading portupgrade

2006-01-02 Thread Jack Raats
Hi,

Running the new portupgrade 2.0.0,1 gives the following errors:

orac# portupgrade -Na
[Updating the portsdb  in /usr/ports ... - 13945 port 
entries found 
.1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.
 . done]
** Package origin of 'bison' has been changed: 'devel/bison' -> 'devel/bison2'
** No need to upgrade 'bison-1.75_2,1' (>= bison-2.1_1). (specify -f to force)
/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:89:in `<<': failed to allocate 
memory (NoMemoryError)
from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:89:in `trace'
from /usr/local/sbin/portupgrade:723:in `do_upgrade'
from /usr/local/sbin/portupgrade:696:in `main'
from /usr/local/sbin/portupgrade:693:in `each'
from /usr/local/sbin/portupgrade:693:in `main'
from /usr/local/sbin/portupgrade:208:in `initialize'
from /usr/local/sbin/portupgrade:208:in `new'
from /usr/local/sbin/portupgrade:208:in `main'
from /usr/local/sbin/portupgrade:1893

Anyone know how to cure this error?

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