> Ah! Found it. It's listed in the "setup.py" file. Hmm... I wonder if > that's a problem, because no other file contains any kind of copyright > notice, and there's no LICENSE file. I'd definitely file a bug against > upstream asking them to clarify this, but I honestly don't know if > ftp-master will accept the package as is. Maybe there's some > precedence, but I'm short on time right now and can't really dive into > the archives to find something. Perhaps someone more knowledgeable can > chime in?
Hi Sergio, As an update to this, I filed a bug report upstream. The author originally planned to license as Apache2 but neglected to add the license to the repo (I guess 'MIT' was some default somewhere): see discussion at https://github.com/ericvsmith/dataclasses/issues/123 Anyway, the author has now added the license, but has not yet released a new version, as no code has actually changed. I was wondering if you could help me with regards to packaging based on a specific upstream Git commit rather than a release version, and how that works with the git-buildpackage flow (if it's even allowed/recommended). -Joel
