[MacPorts] #38103: port clean --all all fails to clean py27-pyusb

[MacPorts]

#38103: port clean --all all fails to clean py27-pyusb
-------------------------+--------------------------------
  Reporter:  istlota@…   |      Owner:  macports-tickets@…
      Type:  defect      |     Status:  new
  Priority:  Low         |  Milestone:
 Component:  ports       |    Version:  2.1.3
Resolution:              |   Keywords:
      Port:  py27-pyusb  |
-------------------------+--------------------------------
Changes (by ryandesign@…):

 * cc: istlota@… (removed)
 * cc: ryandesign@… (added)


Old description:

> Once a week, I port clean -all all. This week, it is failing when it gets
> to py27-pyusb with this message:
>
> --->  Cleaning py27-pyusb
>
> ''Error: Unable to open port: couldn't change working directory to
> "/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/python/py27
> -pyusb-devel": no such file or directory''
>

> Yet, I can successfully complete a port clean py27-pyusb, port uninstall
> py27-usb, and port install py27-pyusb.
>
> Five days ago, py27-pyusb-devel was removed, right? This is acting like
> there is some sort of unnecessary py27-pyusb-devel dependency which is
> unique to port clean --all all, but not port clean py27-pyusb. Grok?

New description:

 Once a week, I port clean -all all. This week, it is failing when it gets
 to py27-pyusb with this message:

 {{{
 --->  Cleaning py27-pyusb
 Error: Unable to open port: couldn't change working directory to
 "/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/python/py27
 -pyusb-devel": no such file or directory
 }}}

 Yet, I can successfully complete a port clean py27-pyusb, port uninstall
 py27-usb, and port install py27-pyusb.

 Five days ago, py27-pyusb-devel was removed, right? This is acting like
 there is some sort of unnecessary py27-pyusb-devel dependency which is
 unique to port clean --all all, but not port clean py27-pyusb. Grok?

--

Comment:

 Please verify that the problem still occurs after running "sudo port
 selfupdate". If so, I believe I understand what is happening, and will try
 to explain and fix it.

-- 
Ticket URL: <https://trac.macports.org/ticket/38103#comment:1>
MacPorts <http://www.macports.org/>
Ports system for Mac OS