[needs packaging] pyephem

Available at: http://revu.ubuntuwire.com/details.py?package=pyephem

An update: I got curious as to how things were going, and found that the process got hung up about two months ago on an issue of copyrights (boy, those Debian/Ubuntu people are thorough — well, about copyrights):

http://revu.ubuntuwire.com/details.py?package=pyephem#comment3896

I am working to see whether I can get licensing permission from the authors they have identified. We will see what happens.

*** This is an automated message ***

This bug is tagged needs-packaging which identifies it as a request for a new package in Ubuntu. As a part of the managing needs-packaging bug reports specification, https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-packaging bug reports have Wishlist importance. Subsequently, I'm setting this bug's status to Wishlist.

The copyright issues have been taken care of, and a complete copyright message is now featured in the latest release of the software. It can now be appropriately packaged for Ubuntu. Good luck!

Thanks for reporting (and working on this).

Looking at the publishing history [1], it looks like https://launchpad.net/ubuntu/+source/pyephem has been available in Ubuntu since 16.04. :)

[1] https://launchpad.net/ubuntu/+source/pyephem/+publishinghistory

Was hoping that PyEphem would have been also available for 14.04, but given that there is less than a year before EOL, I doubt that will happen.

Bernmeister: You could look into requesting a backport for 14.04, see https://wiki.ubuntu.com/UbuntuBackports#Requesting_a_Backport for more details. (But as you mention, it is less than a year until it goes EOL)

Thans, I never knew I could request a backport!

Instead I've been providing my own version on my PPA, https://launchpad.net/~thebernmeister/+archive/ubuntu/ppa, as I have an appindicator which uses PyEphem. After Trusty goes EOL, I won't need to provide PyEphem as I presume Debian/Ubuntu will continue to package it.