On Apr 25, 2007, at 17:11, Bakki Kudva wrote:

I have been using Darwinports for a year or so now without any problems. I recently decided I'd have to bite the bullet and upgrade so I did a

sudo port self update

I tested a couple of

sudo port upgrades which went well and so, emboldened I decided to do a

sudo port upgrade outdated

This didn't go without errors. I am attaching a file of errors mostly from attempts to install pkg-config.

The first time around checksum fails. Verifying checksum(s) for pkgconfig Error: Checksum (md5) mismatch for pkg-config-0.21.tar.gz etc.

Then it gets really strange when with each attempt at install, macports seems to append yet another pkgconfig directory to the source dir to look for the tar.gz file. Starting with /opt/local/var/db/dports/distfiles/pkgconfig/pkgconfig/pkg- config-0.21.tar.gz (which is wrong)

and finally ending up with Could not open file: /opt/local/var/db/dports/distfiles/pkgconfig/pkgconfig/pkgconfig/ pkgconfig/pkgconfig/pkgconfig/pkgconfig/pkgconfig/pkgconfig/ pkgconfig/p kgconfig/pkg-config-0.21.tar.gz

Any ideas on what this is?

Also when I try to port uninstall the old ports I still get dependencies against new ports, which they should have. For example: sudo port uninstall ruby @1.8.4_2 ---> Unable to uninstall ruby 1.8.4_2, the following ports depend on it: ---> rb-sqlite3 ---> rb-sqlite3 ---> rb-rubygems

Here one of the rb-sqlite3's is the old one which has been uninstalled. The rb-rubygems is the new active port which shouldn't have dependency on the old version of Ruby. Is it safe to use the -f flag to uninstall an old port? -or- will it remove all dependents even though they are newer?

I'd appreciate any explanation of what's going on and how I might fix it.

pkg-config is required by many other ports. I just confirmed that pkg- config 0.21 still installs just fine. Your bad checksum error probably means your download did not complete successfully. Clean pkgconfig and try again: sudo port clean --all pkgconfig I can't explain the weird pkgconfig/pkgconfig/pkgconfig path in distfiles. I do not know why ports are listed multiple times in the output of port uninstall. I see that too sometimes. I ignore it. Forcing the uninstall is ok if you are going to replace it with a newer version of the port.

Ports Crowd, Using PortAuthority(v2) I tried installing GD2, the first time through there were a bunch of errors at the end, I clicked in the log pane and tried a Cmd-A in order to select the log contents and to my amazement lost the entire log. It turns out Cmd-A is used to select all the ports. So much for the log. Today after speaking to Kevin, the author he pointed out the disk icon that saves the log. I should have spent more time getting familiar with the interface... I restarted the machine, and tried installing gd2_noX11, which was successful. Today I tried installing GD2 again in order to send the log, and this time it appears that all of yesterday's errors are no longer there, however the last few lines in the Port Authority Log showed the following: /usr/bin/install -c -m 644 'gdfontt.h' '/opt/local/var/db/dports/ build/ _opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dp orts_graphics_gd2/work/destroot/opt/local/include/gdfontt.h' /usr/bin/install -c -m 644 'entities.h' '/opt/local/var/db/dports/ build/ _opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dp orts_graphics_gd2/work/destroot/opt/local/include/entities.h' ---> Installing gd2 2.0.34_0 ---> Activating gd2 2.0.34_0 Warning: the following items did not execute (for gd2): com.apple.activate Any ideas how to fix this problem ? Best Regards, Bill Hernandez Plano, Texas

On Apr 28, 2007, at 03:21, Boey Maun Suang wrote:

...

Today I tried installing GD2 again in order to send the log, and this time it appears that all of yesterday's errors are no longer there, however the last few lines in the Port Authority Log showed the following:

/usr/bin/install -c -m 644 'gdfontt.h' '/opt/local/var/db/dports/ build/ _opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate _dports_graphics_gd2/work/destroot/opt/local/include/gdfontt.h' /usr/bin/install -c -m 644 'entities.h' '/opt/local/var/db/dports/ build/ _opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate _dports_graphics_gd2/work/destroot/opt/local/include/entities.h' ---> Installing gd2 2.0.34_0 ---> Activating gd2 2.0.34_0 Warning: the following items did not execute (for gd2): com.apple.activate

Any ideas how to fix this problem ?

I'm pretty sure that the problem is that gd2 and gd2-nox11 cannot be active simultaneously due to requiring files with identical names to be placed in identical locations. If Port Authority has an option to execute port verbosely or with debug output, you should be able to see that in the log. To fix this, just deactivate gd2-nox11 before installing gd2.

I took over maintenance of gd2 when the port went nomaintainer, and I upgraded it to 2.0.34 when that was released. Then I discovered gd2-nox11, and decided I'd better become maintainer of that as well, but did not update it to 2.0.34 yet or do anything else to it. I did not understand why there was a separate gd2-nox11 port. In other cases when it is desired to omit x11 support, a no_x11 variant is created. (See the graphviz port, for example.) I thought maybe it was so that ports could depend on gd2-nox11, but no ports depend on it. Greg, can you shed some light on this? I would prefer to have a single gd2 port with a no_x11 variant, unless there's a compelling reason not to do that.