py27-pygrib installation failure
We had a group of people trying to install a number of packages with MacPorts, including py27-pygrib. For some reason, two people in the group were able to get it to install but four others were not. I checked the bug tracking database, and I found that we have the problem already reported in this report from six weeks ago: https://trac.macports.org/ticket/36470 I don't understand why two of our group did not have trouble, but it may depend on the exact versions of Xcode, etc. Can we just go in and change the code on our machines (to the code suggested in one of the bug comments) and have MacPorts complete the installation or do we have to wait for the port to be updated? Thanks, ++Eric ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: py27-pygrib installation failure
Thanks, Jeremy! On 11/15/12 8:35 AM, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: Can we just go in and change the code on our machines (to the code suggested in one of the bug comments) and have MacPorts complete the installation or do we have to wait for the port to be updated? You can certainly edit the package's source code yourself but it would be easier to just grab the new version when it gets pushed through. I'm adding myself to the ticket: if I get some time I'll update it today. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: xemacs fails to build with new libpng
Jeremy, Thanks for the suggestion, but this did not work for me yesterday. The xemacs build still failed (after a lot of time recompiling things). Today, the new update for xemacs (thanks to Dan Ports!) fixed it and all my ports now build again. The new system of checking the binaries at the end caught a partially built binary and fixed that also. ++Eric On 9/4/12 3:10 PM, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: Now MacPorts won't let me deactivate libpng 1.5 because a number of ports are depending on it. Is there a way to roll back all of the ports to the versions that use libpng 1.4 while things are being sorted out? The xemacs program is something I use all the time. The likely quick fix for this situation is to rebuild xemacs from source: sudo port clean xemacs sudo port -s upgrade --force xemacs If something more intensive than linking against the new libpng libraries needs done, then you should see about setting up a local repository checked out from before libpng's upgrade: https://trac.macports.org/wiki/howto/InstallingOlderPort ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
xemacs fails to build with new libpng
Hi, It seems that xemacs is another casualty of the change to the libpng 1.5 API. I already filed a ticket. Unfortunately, it seems that my existing old copy of xemacs no longer runs because it was dynamically linked to the old version of the libpng library. I was in the middle of running port upgrade outdated when I hit the problem with grace (for which I see there is already a ticket) and xemacs. Now MacPorts won't let me deactivate libpng 1.5 because a number of ports are depending on it. Is there a way to roll back all of the ports to the versions that use libpng 1.4 while things are being sorted out? The xemacs program is something I use all the time. Thanks, ++Eric Fielding ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: xemacs fails to build with new libpng
Dan, Thanks for your very fast fix for the xemacs build! ++Eric On 9/4/12 3:23 PM, Dan Ports dpo...@macports.org wrote: The port didn't build with libpng 1.5. Should be fixed with r97398. Dan -- Dan R. K. PortsUW CSEhttp://drkp.net/ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Upgraded (partially?) to v2.0.3, now port updates fail, OSX 10.6.8
On 10/5/11 6:45 PM, Ryan Schmidt ryandes...@macports.org wrote: On Oct 5, 2011, at 09:50, Fielding, Eric J (3242) wrote: I upgraded to MacPorts v2.0.3 when a recent port selfupdate recommended this. It ran for a long time doing the conversion, and after about 20 minutes, I stopped it. Now it seems that my MacPorts directories are corrupted. The conversion of installed ports to MacPorts 2 format can take several hours, depending on how many you have installed and how fast your disk is. I'm not certain how to instruct MacPorts to attempt the conversion again, now that you interrupted it. Thanks for your reply and explanation. It might be a good idea to add a warning when the conversion starts that it could take a very long time so others don't make my mistake. I should probably just start over from scratch, to avoid future problems with a partial conversion. I see the uninstall directions at http://guide.macports.org/chunked/installing.macports.uninstalling.html so I will use those. Thanks, ++Eric ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Upgraded (partially?) to v2.0.3, now port updates fail, OSX 10.6.8
On 10/6/11 7:17 AM, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: Thanks for your reply and explanation. It might be a good idea to add a warning when the conversion starts that it could take a very long time so others don't make my mistake. I should probably just start over from scratch, to avoid future problems with a partial conversion. I see the uninstall directions at http://guide.macports.org/chunked/installing.macports.uninstalling.html so I will use those. You might try running selfupdate again (with -d so you can watch what's going on). It might find that there are packages remaining to be converted and pick up where it left off. Might. Thanks for the suggestion, but unfortunately, that does not work. The selfupdate seems to think the conversion is complete so it doesn't convert the parts that are missing. == port selfupdate -d --- Updating MacPorts base sources using rsync MacPorts base version 2.0.3 installed, MacPorts base version 2.0.3 downloaded. --- Updating the ports tree --- MacPorts base is already the latest version The ports tree has been updated. To upgrade your installed ports, you should run port upgrade outdated = The port upgrade command still fails in the same way. I also tried running the gentle sudo port -fp uninstall --follow-dependents installed command but that fails with the same problems that the directories are not empty, so I think my only option now is to nuke the whole directory tree. ++Eric ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Upgraded (partially?) to v2.0.3, now port updates fail, OSX 10.6.8
I upgraded to MacPorts v2.0.3 when a recent port selfupdate recommended this. It ran for a long time doing the conversion, and after about 20 minutes, I stopped it. Now it seems that my MacPorts directories are corrupted. When I ran sudo port upgrade outdated I had several port updates refuse to activate. I was able to override them with the force flag. Now I reached the gdk-pixbuf2 package and it refuses to update because it can't uninstall. = --- Computing dependencies for gdk-pixbuf2 --- Cleaning gdk-pixbuf2 --- Uninstalling gdk-pixbuf2 @2.22.1_1 Error: Target org.macports.uninstall returned: error deleting /opt/local/var/macports/software/gdk-pixbuf2/2.22.1_1: directory not empty Log for gdk-pixbuf2 is at: /opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_gdk-pixbuf2_2.22.1_1/gdk-pixbuf2/main.log Warning: Failed to execute portfile from registry for gdk-pixbuf2 @2.22.1_1 --- Uninstalling gdk-pixbuf2 @2.22.1_1 Error: Uninstall gdk-pixbuf2 2.22.1_1 failed: error deleting /opt/local/var/macports/software/gdk-pixbuf2/2.22.1_1: directory not empty To report a bug, see http://guide.macports.org/#project.tickets Do I need to erase all of MacPorts and start over? Or should I just delete the files in the directories where it complains? OSX 10.6.8 Thanks, ++Eric ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
