Re: Upgrade errors.
On May 29, 2009, at 23:26, Frank J. R. Hanstick wrote: On May 29, 2009, at 11:46 AM, Ryan Schmidt wrote: On May 29, 2009, at 12:49, Frank J. R. Hanstick wrote: Error: No port perl5.9 found. Error: No port render found. Error: No port render found. It seems that I did this once before to clear up these problems, so why are they back? Some previous upgrade must have reinstalled these items since the last clearing of the problem. The ports no longer exist so they cannot have been reinstalled. But possibly, back when they did exist, you installed a port which depended on them, and that dependency is still noted in your registry. You should identify which ports those are, and forcibly rebuild them, to get them to record its dependencies correctly. e.g.: sudo port -nf upgrade whateverport Except that once the ports were removed by the actions taken, they only way they could have come back is if the earlier installed ports were upgraded and reloaded them. It still does not make any sense. Which actions taken? Which ports did you rebuild? ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Upgrade errors.
Hello, I have put on this posting forum everything that was rebuilt since the last time the error appeared to indicate what worked and what has not since there were many that have had one problem or another that needed correcting. There have been so many that I do not know for sure which one(s) it would have been. I only know that I reported this some time back, took the steps to correct the problem and now they are back. Is there a way to determine when ports were upgraded last? On May 30, 2009, at 11:59 PM, Ryan Schmidt wrote: On May 29, 2009, at 23:26, Frank J. R. Hanstick wrote: On May 29, 2009, at 11:46 AM, Ryan Schmidt wrote: On May 29, 2009, at 12:49, Frank J. R. Hanstick wrote: Error: No port perl5.9 found. Error: No port render found. Error: No port render found. It seems that I did this once before to clear up these problems, so why are they back? Some previous upgrade must have reinstalled these items since the last clearing of the problem. The ports no longer exist so they cannot have been reinstalled. But possibly, back when they did exist, you installed a port which depended on them, and that dependency is still noted in your registry. You should identify which ports those are, and forcibly rebuild them, to get them to record its dependencies correctly. e.g.: sudo port -nf upgrade whateverport Except that once the ports were removed by the actions taken, they only way they could have come back is if the earlier installed ports were upgraded and reloaded them. It still does not make any sense. Which actions taken? Which ports did you rebuild? Frank J. R. Hanstick tro...@comcast.net ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Upgrade errors.
On 2009-5-29 15:36, Bryan Blackburn wrote: On Thu, May 28, 2009 at 09:35:57PM -0700, Frank J. R. Hanstick said: Hello, I got the following errors following: [...] Error: No port perl5.9 found. Error: No port render found. Error: No port render found. are about. I may have seen these before; but, cannot remember when or why. perl5.9 was renamed perl5.9-devel over a year ago [1], then deleted about a month after that [2] in favor of the release-status perl5.10. Depending on what you're doing with it, going with perl5.10 is probably the best choice. The render port was removed [3] in favor of xorg-renderproto after being a stub port for a while. Just force-uninstall render and you should be fine as it should have been only a build-time dependency and xorg-renderproto takes care of that now. Unfortunately MacPorts doesn't have any sort of support for renaming/deleting ports so this kind of issue occasionally surfaces. It'll be a little better in 1.8 since trying to run an action on a port that is installed but not available in the ports tree has been demoted from an error to a warning. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Upgrade errors.
Hello, It seems that I did this once before to clear up these problems, so why are they back? Some previous upgrade must have reinstalled these items since the last clearing of the problem. On May 28, 2009, at 10:36 PM, Bryan Blackburn wrote: On Thu, May 28, 2009 at 09:35:57PM -0700, Frank J. R. Hanstick said: Hello, I got the following errors following: [...] Error: No port perl5.9 found. Error: No port render found. Error: No port render found. are about. I may have seen these before; but, cannot remember when or why. perl5.9 was renamed perl5.9-devel over a year ago [1], then deleted about a month after that [2] in favor of the release-status perl5.10. Depending on what you're doing with it, going with perl5.10 is probably the best choice. The render port was removed [3] in favor of xorg-renderproto after being a stub port for a while. Just force-uninstall render and you should be fine as it should have been only a build-time dependency and xorg- renderproto takes care of that now. Unfortunately MacPorts doesn't have any sort of support for renaming/deleting ports so this kind of issue occasionally surfaces. Bryan [1] - http://trac.macports.org/changeset/32171 [2] - http://trac.macports.org/changeset/32638 [3] - http://trac.macports.org/changeset/44924 Frank J. R. Hanstick tro...@comcast.net ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users Frank J. R. Hanstick tro...@comcast.net ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Upgrade errors.
On May 29, 2009, at 12:49, Frank J. R. Hanstick wrote: Error: No port perl5.9 found. Error: No port render found. Error: No port render found. It seems that I did this once before to clear up these problems, so why are they back? Some previous upgrade must have reinstalled these items since the last clearing of the problem. The ports no longer exist so they cannot have been reinstalled. But possibly, back when they did exist, you installed a port which depended on them, and that dependency is still noted in your registry. You should identify which ports those are, and forcibly rebuild them, to get them to record its dependencies correctly. e.g.: sudo port -nf upgrade whateverport ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Upgrade errors.
Hello, Except that once the ports were removed by the actions taken, they only way they could have come back is if the earlier installed ports were upgraded and reloaded them. It still does not make any sense. On May 29, 2009, at 11:46 AM, Ryan Schmidt wrote: On May 29, 2009, at 12:49, Frank J. R. Hanstick wrote: Error: No port perl5.9 found. Error: No port render found. Error: No port render found. It seems that I did this once before to clear up these problems, so why are they back? Some previous upgrade must have reinstalled these items since the last clearing of the problem. The ports no longer exist so they cannot have been reinstalled. But possibly, back when they did exist, you installed a port which depended on them, and that dependency is still noted in your registry. You should identify which ports those are, and forcibly rebuild them, to get them to record its dependencies correctly. e.g.: sudo port -nf upgrade whateverport Frank J. R. Hanstick tro...@comcast.net ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Upgrade errors.
Hello, I got the following errors following: sudo port selfupdate sudo port sync sudo port upgrade installed --- Cleaning subversion Error: No port perl5.9 found. Portfile changed since last build; discarding previous state. --- Fetching qemu --- Attempting to fetch qemu-0.10.5.tar.gz from http:// mirror.its.uidaho.edu/pub/savannah//qemu --- Verifying checksum(s) for qemu --- Extracting qemu --- Configuring qemu --- Building qemu Error: Target org.macports.build returned: shell command cd /opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_emulato rs_qemu/work/qemu-0.10.5 make all returned error 2 Command output: audio/coreaudio.c:67: warning: assignment discards qualifiers from pointer target type audio/coreaudio.c:71: warning: assignment discards qualifiers from pointer target type audio/coreaudio.c:75: warning: assignment discards qualifiers from pointer target type audio/coreaudio.c:79: warning: assignment discards qualifiers from pointer target type audio/coreaudio.c:83: warning: assignment discards qualifiers from pointer target type audio/coreaudio.c:87: warning: assignment discards qualifiers from pointer target type audio/coreaudio.c:91: warning: assignment discards qualifiers from pointer target type audio/coreaudio.c:95: warning: assignment discards qualifiers from pointer target type audio/coreaudio.c:99: warning: assignment discards qualifiers from pointer target type audio/coreaudio.c:103: warning: assignment discards qualifiers from pointer target type CCaudio/wavcapture.o CCcurses.o CCvnc.o CCd3des.o OBJC cocoa.o cocoa.m:233: warning: no previous prototype for 'cocoa_keycode_to_qemu' cocoa.m:318:5: warning: __LITTLE_ENDIAN__ is not defined cocoa.m: In function '-[QemuCocoaView toggleFullScreen:]': cocoa.m:426: warning: 'QemuCocoaView' may not respond to '- exitFullScreenModeWithOptions:' cocoa.m:426: warning: (Messages without a matching method signature cocoa.m:426: warning: will be assumed to return 'id' and accept cocoa.m:426: warning: '...' as arguments.) cocoa.m:444: error: 'NSFullScreenModeAllScreens' undeclared (first use in this function) cocoa.m:444: error: (Each undeclared identifier is reported only once cocoa.m:444: error: for each function it appears in.) cocoa.m:445: error: 'NSFullScreenModeSetting' undeclared (first use in this function) cocoa.m:446: warning: 'QemuCocoaView' may not respond to '- enterFullScreenMode:withOptions:' cocoa.m: In function '-[QemuCocoaAppController openPanelDidEnd:returnCode:contextInfo:]': cocoa.m:786: warning: initialization discards qualifiers from pointer target type make: *** [cocoa.o] Error 1 Error: Unable to upgrade port: 1 --- Building qemu Error: Target org.macports.build returned: shell command cd /opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_emulato rs_qemu/work/qemu-0.10.5 make all returned error 2 Command output: OBJC cocoa.o cocoa.m:233: warning: no previous prototype for 'cocoa_keycode_to_qemu' cocoa.m:318:5: warning: __LITTLE_ENDIAN__ is not defined cocoa.m: In function '-[QemuCocoaView toggleFullScreen:]': cocoa.m:426: warning: 'QemuCocoaView' may not respond to '- exitFullScreenModeWithOptions:' cocoa.m:426: warning: (Messages without a matching method signature cocoa.m:426: warning: will be assumed to return 'id' and accept cocoa.m:426: warning: '...' as arguments.) cocoa.m:444: error: 'NSFullScreenModeAllScreens' undeclared (first use in this function) cocoa.m:444: error: (Each undeclared identifier is reported only once cocoa.m:444: error: for each function it appears in.) cocoa.m:445: error: 'NSFullScreenModeSetting' undeclared (first use in this function) cocoa.m:446: warning: 'QemuCocoaView' may not respond to '- enterFullScreenMode:withOptions:' cocoa.m: In function '-[QemuCocoaAppController openPanelDidEnd:returnCode:contextInfo:]': cocoa.m:786: warning: initialization discards qualifiers from pointer target type make: *** [cocoa.o] Error 1 Error: Unable to upgrade port: 1 --- Fetching quartz-wm --- Verifying checksum(s) for quartz-wm --- Extracting quartz-wm --- Configuring quartz-wm --- Building quartz-wm --- Staging quartz-wm into destroot --- Deactivating quartz-wm @1.0.3_0 --- Installing quartz-wm @1.0.3_1 --- Activating quartz-wm @1.0.3_1 --- Cleaning quartz-wm Error: No port render found. Error: No port render found. The qemu error I understand; but, I am not sure what the: Error: No port perl5.9 found. Error: No port render found. Error: No port render found. are about. I may have seen these before; but, cannot remember when or why. Frank J. R. Hanstick tro...@comcast.net ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Upgrade errors.
On Thu, May 28, 2009 at 09:35:57PM -0700, Frank J. R. Hanstick said: Hello, I got the following errors following: [...] Error: No port perl5.9 found. Error: No port render found. Error: No port render found. are about. I may have seen these before; but, cannot remember when or why. perl5.9 was renamed perl5.9-devel over a year ago [1], then deleted about a month after that [2] in favor of the release-status perl5.10. Depending on what you're doing with it, going with perl5.10 is probably the best choice. The render port was removed [3] in favor of xorg-renderproto after being a stub port for a while. Just force-uninstall render and you should be fine as it should have been only a build-time dependency and xorg-renderproto takes care of that now. Unfortunately MacPorts doesn't have any sort of support for renaming/deleting ports so this kind of issue occasionally surfaces. Bryan [1] - http://trac.macports.org/changeset/32171 [2] - http://trac.macports.org/changeset/32638 [3] - http://trac.macports.org/changeset/44924 Frank J. R. Hanstick tro...@comcast.net ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
