Eric ha scritto:
it happens when i run portsnap and then get new ports via:
pkg_version -v | grep \
Use:
pkg_version -Ivl''
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To
Kirill Ponomarew ha scritto:
Please note, it works only if you have updated INDEX file, if not,
just use pkg_version -vL=
He said he used that command just after portsnap, so it is.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
On Thu, Sep 20, 2007 at 09:49:05AM +0200, Alex Dupre wrote:
Eric ha scritto:
it happens when i run portsnap and then get new ports via:
pkg_version -v | grep \
Use:
pkg_version -Ivl''
Please note, it works only if you have updated INDEX file, if not,
just use pkg_version -vL=
-Kirill
On Wed, 19 Sep 2007, Eric wrote:
Anyone have a way to fix this:
snip portsnap output
Building new INDEX files... done.
portconf-1.2! Comparison failed
portmaster-1.9 ! Comparison failed
Version 1.9 is really old, we're up to version 1.20 now.
Doug Barton wrote:
On Wed, 19 Sep 2007, Eric wrote:
Anyone have a way to fix this:
snip portsnap output
Building new INDEX files... done.
portconf-1.2! Comparison failed
portmaster-1.9 ! Comparison failed
Version 1.9 is really old, we're up
Anyone have a way to fix this:
snip portsnap output
Building new INDEX files... done.
portconf-1.2! Comparison failed
portmaster-1.9 ! Comparison failed
it happens when i run portsnap and then get new ports via:
pkg_version -v | grep \
i tried