Date: Thu, 25 Mar 2004 10:13:46 +0800 From: Aeefyu <afu-subscribed-list@aeefyu.net> To: Kent Stewart <kstewart@owt.com> Cc: freebsd-ports@freebsd.org Subject: Re: Probelms and Inconsistencies with Portupgrade Message-ID: <4062405A.2010001@aeefyu.net> In-Reply-To: <200403240732.22548.kstewart@owt.com> References: <4060F9C0.5080102@aeefyu.net> <200403240732.22548.kstewart@owt.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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" 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 has the following as its first few lines:
>>*** Error code 1|||||||
>>Stop in /usr/ports/databases.|||||||
>>Stop in /usr/ports.||||||
>>
>>2. portsdb -Uu reports hundred of make_index error.
>>
>>So, as it is - i cant install new stuff via portupgrade "portinstall
>>-Rv <package>". I seem to be able to maintain it though i.e.
>>"portupgrade -Rv <package>". Anyone can shed light on this matter?
>
>
> There was a time where a "make index" was doing this. Have you tried
> recvsuping ports-all. You need a good index for portupgrade to work. My
> cron job that updated my mirror at 1020 UTC produced an INDEX that
> built without any errors.
Yes. Have blown /usr/ports twice and re-cvsup ports-all.
/usr/ports/INDEX is correct upon update. "portsdb -Uu" will somehow
introduce errors into it.
>
>>I think it might be related to my very very outdated
>>/var/db/pkg/*/CONTENT .. but its just a guess . I cant blow it and
>>start all over again, right? Too risky, this is a production machine.
>
>
> That might affect something else in the pkgtools but not the index. I
> have always used
> cd /usr/ports
> make index
> portsdb -u
>
> The latest portsdb -U uses make index to build INDEX or INDEX-5.
Yes, that was what I was led to believe the function of the command
"portsdb -Uu" :)
However, running that command nowadays seems to corrupt the INDEX :(
I have found a new quirk with my portupgrade:
Running "portinstall -Rv <PACKAGE00>" will actually update all PACKAGE00
dependencies (if needed), however, it wont actually install PACKAGE00.
No errors. No build. Strange.
[1012][root@beta: ports]$ portinstall -Rv editors/vim-lite
---> Session started at: Thu, 25 Mar 2004 10:12:49
** No need to upgrade 'libiconv-1.9.1_3' (>= libiconv-1.9.1_3). (specify
-f to force)
** No need to upgrade 'libtool-1.3.5_2' (>= libtool-1.3.5_2). (specify
-f to force)
---> Reporting the results (+:done / -:ignored / *:skipped / !:failed)
- converters/libiconv (libiconv-1.9.1_3)
- devel/libtool13 (libtool-1.3.5_2)
---> Session ended at: Thu, 25 Mar 2004 10:12:52 (consumed 00:00:03)
--
Feisal
Webcraft Solutions - http://www.webcraftsolutions.com
--------------------------------------
Feel disillusioned? I've got some great new illusions ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4062405A.2010001>