Bug#836677: pysparse: still worth maintaining?

Thanks for your work! Uploaded. Anton 2016-09-23 15:55 GMT+02:00 Ghislain Vaillant : > Hi Anton, > > Following up on your offer for sponsorship. I pushed debian/1.1.1-1 to > the packaging repository after checking the build runs successfully on > debomatic: > > >

Bug#836677: pysparse: still worth maintaining?

Hi Anton, Following up on your offer for sponsorship. I pushed debian/1.1.1-1 to the packaging repository after checking the build runs successfully on debomatic: http://debomatic-amd64.debian.net/distribution#unstable/pysparse/1.1.1-1/buildlog This release will also close the current RC

Bug#836677: pysparse: still worth maintaining?

Hi Ghis, thanks for working on the package! Even it is abandoned by upstream, we have to support it in Debian, because it has reverse-dependency. Feel free to ping me, if one need the package sponsoring. Best regards Anton 2016-09-22 9:33 GMT+02:00 Ghislain Vaillant : > I

Bug#836677: pysparse: still worth maintaining?

I have had a look at updating the package to the newest upstream release and fixing this FTBFS. However, I have got strong concerns as to whether it is worth keeping this package maintained in the archive: - The latest release on PyPI [1] is busted (missing files). The issue was reported [2] but