pkg_version confused by architecutre in package name

[LoN]Kamikaze LoN_Kamikaze at gmx.de
Fri Jul 7 07:17:26 UTC 2006


Brooks Davis wrote:
> On Thu, Jul 06, 2006 at 06:04:37PM +0200, [LoN]Kamikaze wrote:
>> Brooks Davis wrote:
>>> On Thu, Jul 06, 2006 at 11:01:43AM +0200, [LoN]Kamikaze wrote:
>>>> Brooks Davis wrote:
>>>>> On Thu, Jul 06, 2006 at 02:45:45AM +0200, [LoN]Kamikaze wrote:
>>>>>> I normally run the command
>>>>>> #  pkg_version -Iv | grep \<
>>>>>> before running 'portupgrade -a', to see what's going to happen. This time I got the following output:
>>>>>>
>>>>>> diablo-jdk-freebsd6.i386.1.5.0.07.00  <   needs updating (index has 1.5.0.07.00)
>>>>>>
>>>>>> It seems that the tool is confused by the i386 in the package name.
>>>>> Actually I think it's confused by the fact that the package name is
>>>>> "diablo-jdk" and the version is "freebsd6.i386.1.5.0.07.00".  That's
>>>>> just plain bogus.
>>>>>
>>>> So who is at fault? The ports infrastructure or the FreeBSD foundation?
>>> I don't know.  How did you install it?
>> # pkg_add diablo-jdk-freebsd6.i386.1.5.0.07.00.tbz
> 
> It definitly installs correctly if you use the port instead of the
> package.  It looks like the package is incorrect.
> 

Yes, that fixed it. So I guess the FreeBSD foundation is at fault.


More information about the freebsd-ports mailing list