Index not being built again

Erwin Lansing erwin at
Thu Oct 25 07:15:04 UTC 2012

On Wed, Oct 24, 2012 at 10:21:45AM -0700, Kevin Oberman wrote:
> After two days of having no ports to update on any systems I built the
> index myself and:
> ldns-1.6.13_1               <  needs updating (port has 1.6.14)
> libevent2-2.0.19            <  needs updating (port has 2.0.20)
> libvdpau-0.5                <  needs updating (port has 0.5_1)
> lighttpd-1.4.31_4           <  needs updating (port has 1.4.31_5)
> mosh-1.2.3                  <  needs updating (port has 1.2.3_1)
> openjdk6-b26_1              <  needs updating (port has b26_2)
> portmaster-3.14_5           <  needs updating (port has 3.14_6)
> wireshark-1.8.2_1           <  needs updating (port has 1.8.3)
> xterm-284                   <  needs updating (port has 284_1)
> Looks like the index build is broken again or I have some problem that
> is common to all of my systems. Since the recent issue, I suspect that
> it is the former.

Yes, INDEX is broken by the following commit:
There are duplicate pgtcl ports.

As Mark said earlier, there has been both a lot of work on the physical
machines and we moved the backend from cvs (via the svn-to-cvs exporter)
to use svn directly, which is why mails of the breakage were turned off
for debugging.  Those mails are turned on again.


Erwin Lansing                          
erwin at                        http://

More information about the freebsd-ports mailing list