pkg versions don't match

[Alejandro Imass]

On Fri, Dec 19, 2014 at 4:14 AM, Alberto Mijares <amijaresp at gmail.com>
wrote:

[...]


> Try this:
>
> # pkg -f update
>
> and then try to install fail2ban again.
>
>
>
Alberto, thanks for the tip but -f says illegal option looked in man and it
does not exist. This is a fresh 10.0-RELEASE install so it came with pkg
preinstalled and no need for pkg2ng AFAICR. Anyway it was working just fine
but it seems the versions in remote do not match the versions in my local
pkgng database, even though it says is all up to date!

root at poseidon:/etc/pkg # pkg update
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
root at poseidon:/etc/pkg # pkg install py27-fail2ban
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
The following 6 packages will be affected (of 0 checked):

New packages to be INSTALLED:
        py27-fail2ban: 0.9.0_2
        python27: 2.7.8_4
        python2: 2_3
        py27-setuptools27: 5.5.1
        py27-sqlite3: 2.7.8_5
        sqlite3: 3.8.6

The process will require 68 MB more space.
10 MB to be downloaded.

Proceed with this action? [y/N]: y
pkg:
http://pkg.FreeBSD.org/freebsd:10:x86:64/latest/All/py27-fail2ban-0.9.0_2.txz:
Not Found

Best,

-- 
Alejandro Imass