On Mon, 27 Jan 2020, Sandro Tosi wrote: > in the archive we have 0.5.3, released in 2015; the latest upstream > release is 0.5.7 which was released in 2017; the first release to > support python3 is 0.5.4 of 2016.
> I see 2 paths forward: > 1. (longer) the package gets upgraded to 0.5.7 (with a relative mini > transition i guess) and that includes adding python3-freenect and drop > python-freenect > 2. (shorter) we keep 0.5.3 and we simply drop python-freenect, which > has 0 reverse dependencies in the archive. > What do you think it's best here? I would have tried going "longer" way, given the age of 0.5.3. Would you have time for it Sandro, or should I try? Cheers, -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
