This is probably the hardest - post in data to pearweb to change the package's source location.
we'd need an API for PEARweb
For now, I've updated the shell scripts to tell users to edit the package web page.
One minor change which I'll have to do to pearweb anyway - many of the pages link to the old cruise control instance.
pearweb overview page fix is out, pointing at the right spot. I've been just monitoring when migrations happen and manually updating for now where it's not consistent.
It's only a few hundred packages, and seems quicker to do it that way.