Whoops, totally missed that macs2 was already packaged as `macs` (I only search for macs2 as that was the name in PyPI).
FYI: upstream has stopped updating the GitHub tags & releases and switched to PyPI. Differences between macs 2.0.9 and macs2 version 2.1.0 in my package - Upstream's license is now BSD-3-clause - Single binary with subcommands - Has two spelling errors (I patched this) Different packaging choices I made (mostly related to 2015 best practices vs. 2012) - pybuild - upstream/metadata for their paper - used Git instead of Subversion - watch looks at PyPI (bonus, upstream signs their releases now!) Shall I migrate the subversion repository to git and then apply my changes? My git repo is at git+ssh://git.debian.org/git/debian-med/macs2.git
