Changes between Initial Version and Version 1 of Ticket #38103, comment 4


Ignore:
Timestamp:
Feb 18, 2013, 3:31:06 AM (12 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #38103, comment 4

    initial v1  
    11I believe the following is correct:
    22
    3 In r103036 the unified ports py-pyusb and py-pyusb-devel were created by copying and modifying py26-pyusb and py26-pyusb-devel. The new unified ports contain subports for python25, python26 and python27. When converting non-unified ports to a unified port, it is necessary to create the new unified port and also to delete all the old non-unified ports in the same commit. In r103036 py26-pyusb and py26-pyusb-devel were deleted, but it was not realized that a standalone py27-pyusb-devel existed, so it was not deleted. When the server-side portindex process ran following r103036, the py27-pyusb-devel subport of py-pyusb-devel was not added to the index because that conflicted with the existing standalone py27-pyusb-devel port. A duplicate key error message was produced by the server-side portindex process, which caused an automated email about this problem to be sent to our administrator, in response to which he [https://lists.macosforge.org/pipermail/macports-dev/2013-February/022019.html alert the dev mailing list] to the problem, which led to Rainer removing the old py27-pyusb-devel port in r103042. But MacPorts doesn't know that it should now re-index the py-pyusb-devel port, so the index still contains the old path for the now-deleted py27-pyusb-devel port.
     3In r103036 the unified ports py-pyusb and py-pyusb-devel were created by copying and modifying py26-pyusb and py26-pyusb-devel. The new unified ports contain subports for python25, python26 and python27. When converting non-unified ports to a unified port, it is necessary to create the new unified port and also to delete all the old non-unified ports in the same commit. In r103036 py26-pyusb and py26-pyusb-devel were deleted, but it was not realized that a standalone py27-pyusb-devel existed, so it was not deleted. When the server-side portindex process ran following r103036, the py27-pyusb-devel subport of py-pyusb-devel was not added to the index because that conflicted with the existing standalone py27-pyusb-devel port. A duplicate key error message was produced by the server-side portindex process, which caused an automated email about this problem to be sent to our administrator, in response to which he [https://lists.macosforge.org/pipermail/macports-dev/2013-February/022019.html alerted the dev mailing list] to the problem, which led to Rainer removing the old py27-pyusb-devel port in r103042. But MacPorts doesn't know that it should now re-index the py-pyusb-devel port, so the index still contains the old path for the now-deleted py27-pyusb-devel port.
    44
    55The solution should therefore be to make any change to the py-pyusb-devel port so that the server-side process re-indexes it. I've made such a change in r103179. Please wait 30 minutes, then run "sudo port selfupdate" and verify whether it's fixed.