https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204567
--- Comment #10 from John W. O'Brien <j...@saltant.com> --- (In reply to graham from comment #8) I'm sorry for the delay. I tried to post a response a day or two ago, but it appears to have been lost. It has been many moons since I last used portupgrade, so my chops are rusty to say the least. However, this patch registers the new name in MOVED, so I believe that it meets its requirements w.r.t. the ports infrastructure. portupgrade has been MOVED-aware since v2.4.9.8 according to the latest release notes (https://github.com/freebsd/portupgrade/blob/2.4.14/NEWS.md). My main hint is to investigate the "-o" option for portupgrade. If neither of these leads proves fruitful, please provide more detail about the state of your system (versions of FreeBSD and portupgrade, at least, and the update method and relative snapshots of the ports tree) and the things you have tried (detailed command lines and full output as an attachment), to help us determine if this is a port-specific regression or a portupgrade support issue. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ freebsd-python@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
