On Tue, Dec 21, 2010 at 08:17:27PM +, Paul Macdonald wrote:
> On 21/12/2010 19:29, Chuck Swiger wrote:
> > On Dec 21, 2010, at 10:53 AM, Paul Macdonald wrote:
> >> I have a couple of older boxes on freebsd 6 that are reporting ports
> >> succeeding index, even after a fresh index has been down
On 21/12/2010 19:29, Chuck Swiger wrote:
On Dec 21, 2010, at 10:53 AM, Paul Macdonald wrote:
I have a couple of older boxes on freebsd 6 that are reporting ports succeeding
index, even after a fresh index has been downloaded.
e.g
portupgrade-2.4.8_1,2>succeeds index (index has 2.4.8,2)
spam
On Dec 21, 2010, at 10:53 AM, Paul Macdonald wrote:
> I have a couple of older boxes on freebsd 6 that are reporting ports
> succeeding index, even after a fresh index has been downloaded.
> e.g
> portupgrade-2.4.8_1,2 > succeeds index (index has 2.4.8,2)
> spamass-milter-0.3.1_11 > succeeds i
I have a couple of older boxes on freebsd 6 that are reporting ports
succeeding index, even after a fresh index has been downloaded.
e.g
portupgrade-2.4.8_1,2 > succeeds index (index has 2.4.8,2)
spamass-milter-0.3.1_11 > succeeds index (index has 0.3.1_10)
i had figured something screwy w