Problem with index

Jason E. Hale jhale at
Mon Feb 20 13:52:48 UTC 2017

On Mon, Feb 20, 2017 at 7:41 AM, Tijl Coosemans <tijl at> wrote:
> On Mon, 20 Feb 2017 12:29:47 +0000 Matthew Seaman <matthew at> wrote:
>> On 2017/02/20 11:36, Gerard Seibert wrote:
>>> I just updated my ports tree using "portsnap". I then ran the following
>>> command:
>>> /usr/sbin/pkg version -vL=
>>> This resulted in the following message:
>>> postfix-current-3.2.20170129,4     >   succeeds index (index has 3.2.0.r1,4)
>>> This does not seem correct. What is happening and how do I correct it?
>> Your index file is out of date -- portsnap doesn't updated it because it
>> changes too fast to be suitable for keeping in SVN.
>> You need to
>>   # make fetchindex
>> from /usr/ports to download a pre-built index.  Or build your own, by
>> 'make index'.  Or tell 'pkg version' to compare versions directly with
>> what's in your ports tree by 'pkg version -vP=' (but this will be quite
>> a bit slower).
> Portsnap should update the INDEX file.  Check /etc/portsnap.conf.  There
> should be a line like this: INDEX INDEX-<N> DESCRIBE-<N> where <N> is the
> major version of the FreeBSD release you have installed (10, 11 or 12).

Your INDEX is probably fine. I think this is simply a case of
PORTEPOCH not getting bumped on the last update of
mail/postfix-current. 3.2.20170129,4 is numerically greater than the
current version of 3.2.0.r1,4. PORTEPOCH should be bumped to 5.
Maintainer of mail/postfix-current CC'd.

More information about the freebsd-ports mailing list