ports/116132: Python 2.4 -> 2.5 upgrade leaves meta-package at 2.4.

[Michael P. Soulier]

>Number:         116132
>Category:       ports
>Synopsis:       Python 2.4 -> 2.5 upgrade leaves meta-package at 2.4.
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Sep 05 18:50:01 GMT 2007
>Closed-Date:
>Last-Modified:
>Originator:     Michael P. Soulier
>Release:        FreeBSD 5.5-STABLE i386
>Organization:
>Environment:
System: FreeBSD kanga.digitaltorque.ca 5.5-STABLE FreeBSD 5.5-STABLE #0: Fri Mar 23 18:01:20 EDT 2007 root at kanga.digitaltorque.ca:/usr/obj/usr/src/sys/GENERIC i386


	AMD Duron, PCI-based PC
>Description:
	I upgraded Python 2.4 -> 2.5 following this command in UPDATING.
    portupgrade -o lang/python25 lang/python24

    Unfortunately, this leaves the python metapackage at python 2.4, so when I
    then run portupgrade -a, it wants to upgrade again, rebuilding python 2.5
    yet again. 

    [msoulier at kanga ~]$ pkg_info | grep python
    mod_python-3.3.1    Apache module that embeds the Python interpreter
    within the
    python-2.4.4,1      The "meta-port" for the stable version of Python
    interprete
    python25-2.5.1      An interpreted object-oriented programming language

    Should not a python upgrade procedure include a process to pull the meta
    package forward?
>How-To-Repeat:
	Install python 2.4 from older ports snapshot when 2.4 was current,
    installing via the python metapackage. Then update to the latest ports
    snapshot and upgrade python using the instructions in UPDATING.
>Fix:
    Upgrade the python metapackage, rebuilding python 2.5 yet again.
>Release-Note:
>Audit-Trail:
>Unformatted: