kdepim3 build fails

[gallafent]

When I attempt to do a "port upgrade outdated", the process fails while trying to build kdepim3. I'm not even sure why kdepim3 is being installed, so I have attempted, fruitlessly, to uninstall it, and to work out why it is trying to be installed! Fragment of session:

Humber:~ williamg$ sudo port clean --all kdepim3
--->  Cleaning kdepim3
Humber:~ williamg$ sudo port uninstall kdepim3
Humber:~ williamg$ sudo port upgrade outdated
--->  Computing dependencies for kdepim3
--->  Fetching archive for kdepim3
--->  Attempting to fetch kdepim3-3.5.10_1.darwin_11.x86_64.tbz2 from http://packages.macports.org/kdepim3
--->  Fetching kdepim3
--->  Attempting to fetch kdepim-3.5.10.tar.bz2 from http://lil.fr.distfiles.macports.org/kde3
--->  Attempting to fetch kde-admindir-1502.tar.bz2 from http://lil.fr.distfiles.macports.org/kde3
--->  Verifying checksum(s) for kdepim3
--->  Extracting kdepim3
--->  Configuring kdepim3
--->  Building kdepim3
Error: Target org.macports.build returned: shell command failed (see log for details)
Log for kdepim3 is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_kde_kdepim3/kdepim3/main.log
Error: Problem while installing kdepim3
To report a bug, see <http://guide.macports.org/#project.tickets>
Humber:openvpnstuff williamg$ port dependents kdepim3
Error: Registry error: kdepim3 not registered as installed.
Humber:openvpnstuff williamg$ port rdependents kdepim3
Error: Registry error: kdepim3 not registered as installed.

I will attach my main.log.

It appears that the some of the network fetches fail, but it seems to carry on past those problems.

I see that there's no maintainer for this port, happy to try to fix it if somebody can indicate to me what's going on - at the moment I don't understand what's going wrong!

[gallafent]

main.log of attempted build of kdepim3

[gallafent]

Cc Me!

[mf2k (Frank Schima)]

The reporter is automatically Cc'ed.

[fleason (Fred Leason)]

Cc Me!

[gallafent]

This bug now appears to have “fixed itself” …