Available Ports

[Ryan Schmidt]

On Oct 7, 2015, at 8:18 PM, Manfred Antar wrote:

> I’m seeing something wierd here too:
> 
> (macports)3529}port -v sync
> --->  Updating the ports tree
> Synchronizing local ports tree from rsync://rsync.macports.org/release/tarballs/ports.tar
> receiving file list ... done
> ports.tar
> 
> sent 55526 bytes  received 112 bytes  22255.20 bytes/sec
> total size is 62689280  speedup is 1126.73
> receiving file list ... done
> ports.tar.rmd160
> 
> sent 64 bytes  received 117 bytes  120.67 bytes/sec
> total size is 512  speedup is 2.83
> Creating port index in /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports
> Warning: failed to open old entry for devel/dbus-python, making a new one
> Adding port devel/dbus-python
> Adding subport dbus-python27
> Adding subport dbus-python34
> Failed to parse file devel/dbus-python/Portfile with subport 'dbus-python35': couldn't execute "/opt/local/bin/python3.5-config": no such file or directory
> Adding subport dbus-python24
> Adding subport dbus-python25
> Adding subport dbus-python26
> Adding subport dbus-python31
> Adding subport dbus-python32
> Adding subport dbus-python33
> 
> Total number of ports parsed:	10 
> Ports successfully parsed:	9 
> Ports failed:			1 
> Up-to-date ports skipped:	24823
> 
> keep getting error about dbus-python35
> I don’t have python35 installed

Thanks for reporting that!

In fact, if you had python35 installed, you wouldn't see the error.

This is a bug in the dbus-python port, and may be the cause of the index failure on the server.

I've filed a bug report:

https://trac.macports.org/ticket/49180