portmanager behaviour

2007-02-07 Thread pete wright

hi all, i was wondering if anyone else ran into a problem recently
when portmanager was moved to /usr/ports/ports-mgt/portmanger.  i have
a nightly cron which runs a portmanager -s to give me a status
report in the morning on outdated ports.  i believe when the move
occurred that portmanager removed itself from the system.  anyone else
see this?

-pete

--
~~o0OO0o~~
Pete Wright
www.nycbug.org
NYC's *BSD User Group
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: portmanager behaviour

2007-02-07 Thread Gerard Seibert
On Wednesday February 07, 2007 at 12:44:30 (PM) pete wright wrote:


 hi all, i was wondering if anyone else ran into a problem recently
 when portmanager was moved to /usr/ports/ports-mgt/portmanger.  i have
 a nightly cron which runs a portmanager -s to give me a status
 report in the morning on outdated ports.  i believe when the move
 occurred that portmanager removed itself from the system.  anyone else
 see this?

If you did not do so already, update your ports tree, then update
'portmanager'. You need to use 'make install' since portmanager cannot
update itself.

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


Re: portmanager behaviour

2007-02-07 Thread youshi10

On Wed, 7 Feb 2007, pete wright wrote:


hi all, i was wondering if anyone else ran into a problem recently
when portmanager was moved to /usr/ports/ports-mgt/portmanger.  i have
a nightly cron which runs a portmanager -s to give me a status
report in the morning on outdated ports.  i believe when the move
occurred that portmanager removed itself from the system.  anyone else
see this?

-pete

--
~~o0OO0o~~
Pete Wright
www.nycbug.org
NYC's *BSD User Group


Check your cron logs or email from the cron daemon to see whether or not this 
is the case--shouldn't be.

Instead ports related items should just be failing right now because it's 
looking for the ports dependencies in the old directories (sys-tools/*).
-Garrett

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