On Wed, 24 Mar 2004 1:00 pm, Aeefyu wrote:
Deal All,
My problems surfaced when I updated Portupgrade with reference to
item 20040226 in /usr/ports/UPDATING (though I suspect this is just
a catalyst -- actual problem lies elsewhere)
I had a similar problem. I saw another thread where they
anubis wrote:
My problems surfaced when I updated Portupgrade with reference to
item 20040226 in /usr/ports/UPDATING (though I suspect this is just
a catalyst -- actual problem lies elsewhere)
I had a similar problem. I saw another thread where they suggested
getting rid of your refuse file,
On Thursday 25 March 2004 01:46 am, Aeefyu wrote:
anubis wrote:
My problems surfaced when I updated Portupgrade with reference to
item 20040226 in /usr/ports/UPDATING (though I suspect this is just
a catalyst -- actual problem lies elsewhere)
I had a similar problem. I saw another thread
Aeefyu [EMAIL PROTECTED] writes:
Have been cvsup-ing for couple of days with the same
results. /usr/ports/INDEX is updated correctly, but will have errors
once I run portsdb -Uu. As of yesterday, I am skipping the portsdb
-Uu step after cvsup-ing ports-all. This is NOT a correct behaviour
Lowell Gilbert wrote:
Aeefyu [EMAIL PROTECTED] writes:
Have been cvsup-ing for couple of days with the same
results. /usr/ports/INDEX is updated correctly, but will have errors
once I run portsdb -Uu. As of yesterday, I am skipping the portsdb
-Uu step after cvsup-ing ports-all. This is NOT a
Aeefyu [EMAIL PROTECTED] writes:
Deal All,
My problems surfaced when I updated Portupgrade with reference to item
20040226 in /usr/ports/UPDATING (though I suspect this is just a
catalyst -- actual problem lies elsewhere)
My production box is currently running on 4.9-RELEASE-p4 (this box
Lowell Gilbert wrote:
Aeefyu [EMAIL PROTECTED] writes:
I have reinstall manually portupgrade and ruby* (using make install
clean), rebuild INDEX with portsdb -Uu and pkgdb -fu or pkgdb
-F. Even went to the extent of blowing my /usr/ports and cvsup all
over again. However, :
1. my /usr/ports/INDEX
Kent Stewart wrote:
On Tuesday 23 March 2004 07:00 pm, Aeefyu wrote:
portupgrade -Rv dir/package ie. upgrading a package seems to be
working fine, however. It seems to only affect portinstall
I have reinstall manually portupgrade and ruby* (using make install
clean), rebuild INDEX with portsdb -Uu
Deal All,
My problems surfaced when I updated Portupgrade with reference to item
20040226 in /usr/ports/UPDATING (though I suspect this is just a
catalyst -- actual problem lies elsewhere)
My production box is currently running on 4.9-RELEASE-p4 (this box is
originally a 3.3-RELEASE -and
