Per IRC conversation with mva, I'm sending python@ a list of ports that
currently don't build in DragonFly poudriere due to ports infrastructure
problems.  I have not changed the python default in make.conf.  It would
be nice to get Mk/bsd.python.mk (or whatever) fixed so these ports build
in poudriere again.  Thanks, John

1. graphics/py3-cairo
===>   py33-cairo-1.10.0_1 depends on package:
/packages/All/python-3.3_1,2.txz - not found
http://muscles.dragonflybsd.org/bulk/latest-per-pkg/py33-cairo/1.10.0_1/bleeding-edge-potential.log

2. databases/py-kyotocabinet
===>   py33-kyotocabinet-1.22 depends on package:
/packages/All/python-3.3_1,2.txz - not found
http://muscles.dragonflybsd.org/bulk/latest-per-pkg/py33-kyotocabinet/1.22/bleeding-edge-potential.log

3. databases/py-postgresql
===>   py33-postgresql-1.1.0 depends on package:
/packages/All/python-3.3_1,2.txz - not found
http://muscles.dragonflybsd.org/bulk/latest-per-pkg/py33-postgresql/1.1.0/bleeding-edge-potential.log

4. sysutils/brebis
===>   brebis-0.7 depends on package: /packages/All/python-3.3_1,2.txz -
not found
http://muscles.dragonflybsd.org/bulk/latest-per-pkg/brebis/0.7/bleeding-edge-potential.log

5. sysutils/dvdvideo
===>   dvdvideo-20130117 depends on package:
/packages/All/python-3.3_1,2.txz - not found
http://muscles.dragonflybsd.org/bulk/latest-per-pkg/dvdvideo/20130117/bleeding-edge-potential.log

6. textproc/codespell
===>   codespell-1.6_1 depends on package:
/packages/All/python-3.3_1,2.txz - not found
http://muscles.dragonflybsd.org/bulk/latest-per-pkg/codespell/1.6_1/bleeding-edge-potential.log

7. x11-toolkits/py31-tkinter
===>   py31-tkinter-3.1.5_4 depends on package:
/packages/All/python-3.1_1,2.txz - not found
http://muscles.dragonflybsd.org/bulk/latest-per-pkg/py31-tkinter/3.1.5_4/bleeding-edge-potential.log

_______________________________________________
freebsd-python@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"

Reply via email to