Hi there,

TroveClient just got rejected by Debian FTP masters. Reply from Luke
Faraone is below.

In general, I would strongly advise that a clean COPYRIGHT-HOLDER file
is created with the copyright holders in them. Why? Because it is hard
to distinguish between authors and copyright holders, which are very
distinct things. Listing the authors in debian/copyright doesn't seem to
satisfy the FTP masters as well... :(

FYI, my reply was that I knew some of the authors were working for
Rackspace, because I met them in Portland, and that I knew Rackspace was
one of the copyright holders. Though that's of course not enough for the
Debian FTP masters.

Your thoughts?

Cheers,

Thomas Goirand (zigo)

-------- Original Message --------
Subject: [Openstack-devel] python-troveclient_0.1.4-1_amd64.changes REJECTED
Date: Sat, 19 Oct 2013 04:00:19 +0000
From: Luke Faraone <ftpmas...@ftp-master.debian.org>
To: PKG OpenStack <openstack-de...@lists.alioth.debian.org>, Thomas
Goirand <z...@debian.org>


Dear maintainer,

debian/copyright is **not** an AUTHORS list. This package appears to be
Copyright (c) 2013 Hewlett-Packard Development Company, L.P., and some
other
companies, not copyrighted each individual employee at HP who worked on it.

Your automated debian/copyright generation is most probably suboptimal for
most packages, and is most certainly not a substitute for manual review.
One
missed copyright holder:

python-troveclient-0.1.4\troveclient\base.py:
    Copyright 2010 Jacob Kaplan-Moss

Cheers,

Luke Faraone
FTP Team


===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.


_______________________________________________
Openstack-devel mailing list
openstack-de...@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/openstack-devel




_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to