MPICH 3.0 was released recently (http://mpich.org). In the process of this major release (which is nonetheless backward compatible), they changed the project name from MPICH2 to MPICH. I maintain the mpich2 package on AUR (https://aur.archlinux.org/packages/mpich2/) and would like to upgrade it in the most pain-free way possible. Note that there are several something-mpich2 packages on AUR, and quite a few more package that depend on mpich2. What is the best way to avoid disrupting users during the upgrade?
Last edited by jedbrown (2013-01-01 00:17:22)
The answer is to upload the new version of the package, then write the aur-general mailing list with a request to merge. The issue is now resolved.