On Monday, May 14 2018, Joel Cross wrote: > On Mon, 30 Apr 2018, at 6:21 PM, Joel Cross wrote: >> > 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). >> > Hi again, > > Did you get the chance to think about the above? I will happily > repackage from the git master, but I'm not sure what to do about > version numbers and stuff (and online informaition about this is hard > to find!). Please can you help? Hey Joel, Sorry about the delay, this one fell through the cracks. So, to be honest, I'm not 100% sure how to proceed in this case. I mean, I probably would talk to upstream again and ask them to cut a release after fixing the licensing issue, because IMHO it's an important fix and justifies a new release. But I understand they may not agree. Packaging from git master would probably involve importing upstream's master branch as another branch on your package's repository, and then generating a tarball from there. Or maybe you could follow: https://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.import.upstream-git.html (specifically the "Upstream tarballs and separate upstream history" section). But again, the very first thing I would do is to ask for upstream to cut a (minor?) release containing the license fix. This should be really easy for them to do, and it will really simplify things for you. Please keep me posted and let me know if you need more help. Cheers, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/
Attachment:
signature.asc
Description: PGP signature