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
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
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 \
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
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