2009/12/6 Olly Betts <o...@survex.com> > OK, so just 3 issues remaining: > > The "Copyright (c) The Regents of the University of California" and "THE > REGENTS" in debian/copyright isn't correct for djapian (as its code doesn't > originate at UCB, it just uses the licence). I think that definitely needs > fixing, and now upstream have provided an explicit LICENSE file that's easy > to do.
Done. Do you think it's ok that LICENSE file exists in trunk, but not in released package? Please, take a look at license terms under `Files: debian/*`. Is it correct to use term 'author' instead of full name? I'm still having difficulties understanding legal subtleties. > I'd suggest ensuring debian/copyright and debian/changelog end with a > newline (I'm not aware of this being a requirement, but it's saner for text > files to generally, and less likely to trip up tools which try to parse > them). Done. > And if your VCS is public, adding Vcs- headers to control would be good. New headers added to debian/control: Vcs-Git: git://github.com/uptimebox/python-django-djapian.git Vcs-Browser: http://github.com/uptimebox/python-django-djapian The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/python-django-djapian - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/python-django-djapian/python-django-djapian_2.3-1.dsc Regards, Mikhail -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org