On Sat, September 17, 2016 5:00 pm, trondd wrote: > Daniel Jakots <danj+o...@chown.me> wrote: > >> On Sat, 17 Sep 2016 12:59:01 -0400, "trondd" <tro...@kagu-tsuchi.com> >> wrote: >> >> Yeah, our py-coverage is lagging a bit. If you want to update it, you >> should verify that ports that depend on it doesn't break. I can have a >> look at it if you don't want to do the work. >> >> The list: >> RUN_DEPENDS >> /usr/ports/audio/py-discogs-client >> /usr/ports/devel/py-nosexcover >> /usr/ports/devel/py-nosexcover,python3 >> /usr/ports/devel/py-test-cov >> /usr/ports/devel/py-test-cov,python3 >> TEST_DEPENDS >> /usr/ports/devel/py-nose >> /usr/ports/devel/py-nose,python3 >> /usr/ports/devel/py-nosexcover >> /usr/ports/devel/py-nosexcover,python3 >> /usr/ports/devel/py-smmap >> /usr/ports/net/py-oauth2 >> /usr/ports/security/py-oauthlib >> /usr/ports/security/py-oauthlib,python3 >> /usr/ports/textproc/cdiff >> /usr/ports/textproc/py-polib >> /usr/ports/www/py-beaker >> /usr/ports/www/py-pylons >> /usr/ports/www/py-routes >> /usr/ports/www/py-webtest > > Well right away py-nose failed make test. There hasn't been a realease in > over a year that I can find. >
Bringing this back up as I have some time to look into it further. Turns out the nose 'make test' failures are expected and not a result of updating py-coverage. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828224 I'll check the rest of the dependent ports. Tim.
