?? lang/python27 ?? Why is this even here ?

[Sahil Tandon]

On Sun, 2010-07-25 at 00:38:17 -0400, jhell wrote:

> I guess I should have made it more clear.
> 
> +===========================================+
> | This happened?: 	2010/05/12 12:13:06 |

The above date corresponds to the last commit in lang/python26 at the
time of the repocopy to lang/python27.  As clearly noted in
ports/147784, the repocopy was completed on 2010-07-15, not 2010-05-12.

> | And the date now:	2010/07/25 00:08:51 |
> +===========================================+
> 
> This is more than 2 months that nothing has been done with this port.

I guess you missed revision 1.167 on lang/python26. :) Although the
repocopy was not done two months ago, the 10 day lag between repocopy
and forced commit+actual update is perhaps atypical. Maybe wen@ (who
requested the repocopy) has been busy or waiting for the official
8.1-RELEASE announcement to proceed.  But we can only speculate, so I've
copied him on this reply.

> Unless I am wrong and the repo-copy is recent with an old date but I
> thought that the ident(1) line was/is/should be updated when this happens?.

Yes, the ident(1) line is updated after the repomeister kicks the PR
back to the requesting committer, who then notes the repocopy with a
forced commit.  But you already know this, as you've pasted the relevant
excerpts from the committer's guide in your postscript.  

> After a repo-copy I would have thought that these lines should have been
> updated to establish the new port and for whom created it, which would
> then be re-committed bumping the version to 1.167 and recent date so
> there is no confusion.
> 
> # New ports collection makefile for:    python26
> # Date created:         3 July 2003
> # Whom:                 Hye-Shik Chang <perky at FreeBSD.org>

Yes, this is done concurrently with the commit that actually upgrades
the port to its new version.  For an example, see lang/python31 from
revision 1.158 -> 1.159.

> Any way I just wanted to give a heads up for this as it seemed pretty
> odd as things like this usually happen and get updated all about the
> same time that a repo-copy happens & this has been in ports that I know
> of for more than ~1.5 weeks without any sort of update.

Thanks for your report and patience.  Hopefully wen@ will get to it soon.

-- 
Sahil Tandon <sahil at FreeBSD.org>