Re: devel/py-coverage was [UPDATE] net/gpodder 3.1.0 to 3.9.1

2016-10-05 Thread Alexandr Shadchin
On Thu, Sep 29, 2016 at 10:09:56PM -0400, trondd wrote: > On Sat, September 17, 2016 5:00 pm, trondd wrote: > > Daniel Jakots wrote: > > > >> On Sat, 17 Sep 2016 12:59:01 -0400, "trondd" > >> wrote: > >> > >> Yeah, our py-coverage is lagging a bit. If you want to update it, you > >> should verify

Re: devel/py-coverage was [UPDATE] net/gpodder 3.1.0 to 3.9.1

2016-10-02 Thread Alexandr Shadchin
On Thu, Sep 29, 2016 at 10:09:56PM -0400, trondd wrote: > On Sat, September 17, 2016 5:00 pm, trondd wrote: > > Daniel Jakots wrote: > > > >> On Sat, 17 Sep 2016 12:59:01 -0400, "trondd" > >> wrote: > >> > >> Yeah, our py-coverage is lagging a bit. If you want to update it, you > >> should verify

Re: devel/py-coverage was [UPDATE] net/gpodder 3.1.0 to 3.9.1

2016-09-29 Thread trondd
On Sat, September 17, 2016 5:00 pm, trondd wrote: > Daniel Jakots wrote: > >> On Sat, 17 Sep 2016 12:59:01 -0400, "trondd" >> 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

devel/py-coverage was [UPDATE] net/gpodder 3.1.0 to 3.9.1

2016-09-17 Thread trondd
Daniel Jakots wrote: > On Sat, 17 Sep 2016 12:59:01 -0400, "trondd" > 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_D