jw...@debian.org wrote:
> * Tobias Richter , 2012-03-05, 10:53:
> >>As per Python Policy §3.1, the package name should be python-nxs.
>
> Oops, it actually is Python Policy §2.2:
> http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-package_names
>
> >Thanks for th
* Tobias Richter , 2012-03-05, 10:53:
As per Python Policy §3.1, the package name should be python-nxs.
Oops, it actually is Python Policy §2.2:
http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-package_names
Thanks for the report. I suppose python-nexus would
jw...@debian.org wrote:
> Package: libnexus0-python
> Version: 4.2.1-svn1614-1
>
> As per Python Policy §3.1, the package name should be python-nxs.
Thanks for the report. I suppose python-nexus would be equally acceptable?
I've got a new upstream to package anyway, so this should be addressed s
Package: libnexus0-python
Version: 4.2.1-svn1614-1
As per Python Policy §3.1, the package name should be python-nxs.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
4 matches
Mail list logo