Bug#731975: Changing to RFP
I'm sorry for having kept this as ITP for so long, but I've just decided
that I no longer wish to package pybitmessage for Debian. Feel free to
pick up the work. Before you do, though, here are some things to consider:
-PyBitmessage provides convenience copies of libraries. However, these
cannot be just removed, as there are many local modifications without
which PyBitmessage will not work. They cannot be kept there either, as
Debian policy does not allow shipping convenience copies. I've tried
submitting the PyBitmessage changes to the libraries upstream, although
this is painfully slow.
-PyBitmessage supports Namecoin addresses, but Namecoin is not yet in
Debian. To fix this, you will either have to package Namecoin yourself,
or make a note in the interface explaining that Namecoin is not in
Debian, but it is possible to compile your own Namecoin from source.
-All of the licensing issues have been sorted out, and I've compiled a
list of licenses in this issue:
https://github.com/Bitmessage/PyBitmessage/issues/669 . However, I wrote
that list a while ago, and the licenses may have changed by now.
-Upstream ships a Debian directory, and keeps VCS information in their
release tarballs. You can get around this by using the command 'make
sourcedeb', which generates a .orig.tar.gz without the Debian directory
or the VCS information included.
Good luck, future maintainer! Hopefully, we'll have PyBitmessage in
Debian someday.
Riley Baird
Reply to: