=== arraybolt3_ is now known as arraybolt3
[02:15] <arraybolt3> Possibly weird question, I'm building a debian/copyright file, what do I do when I hit a license that is clearly *supposed* to be a particular well-known license, but that has a bunch of modifications that look like they were either accidental (person trying to type the license from memory maybe?) or for the sake of making it look nicer? I've hit a file with a BSD 3-clause license, but...
[02:16] <arraybolt3> ...they keep omitting the word "above" when talking about the "above copyright notice", and it replaces "Neither the name of the copyright holder nor the names of its contributors may be used" with "The name of the author may not be used".
[02:16] <arraybolt3> Also "THE COPYRIGHT HOLDERS AND CONTRIBUTORS" gets replaced with "THE AUTHOR".
=== arraybolt3_ is now known as arraybolt3
=== popey5 is now known as popey
=== blaze1 is now known as blaze
=== popey6 is now known as popey
=== chrisccoulson_ is now known as chrisccoulson
[20:29] <Eickmeyer[m]> vorlon: Thanks for taking-on the frescobaldi issue. We had someone mistakingly roping-in the Ubuntu Studio ML on it when we don't seed that package. I'd have gladly done it just as a measure of goodwill but ERR:Time.
[21:00] <vorlon> Eickmeyer[m]: no worries
[21:59] <arraybolt3[m]> Random licensing question - is it legal to include a GPL-2+ source code file in a repo that is LGPL-2.1+? Or does that make it so that the whole repo is actually GPL-2+? I'm pretty sure the latter is true, and if so, I have a bit of a mess to untangle.
[22:01] <juliank> arraybolt3[m]: it makes the stuff that uses it (or rather it forms a combined work with) gpl-2+
[22:02] <arraybolt3[m]> Sigh. Yeah, that's what I thought.
[22:02] <juliank> > In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
[22:03] <juliank> but yeah if it's like C code you link into your library you're sol
[22:09] <arraybolt3[m]> Yep. Alright, guess I have some problems to deal with then.
[22:54] <vorlon> rbasak: why is wike not in git-ubuntu? (sru currently in the queue)
[22:58] <rbasak> vorlon: I'll do that manually for you now.
[22:59] <vorlon> that wasn't the question! :)
[22:59] <rbasak> :)
[22:59] <vorlon> rbasak: I've already accepted the SRU :)
[22:59] <rbasak> The reason is that the code change that imports everything hadn't landed yet. Prior to that it was only packages that existed at the time I imported everything.
[22:59] <vorlon> ah
[23:00] <rbasak> That MP is now Approved but I'm on vacation for a week now. I'll put it into production when I get back.
[23:00] <rbasak> I'll leave wike for now then.
[23:01] <rbasak> So to be clear, everything that is already imported will continue being updated. Anything new that's not in main needs manually importing once, which I've already done for packages that existed at the time.
[23:01] <rbasak> When I land the MP to fix this, I'll catch up everything new since that point, and then we should be good.
[23:01] <vorlon> got it, thanks
[23:04] <rbasak> Oh and there are some exceptional packages that have edge case import failures. ~50. I've been working on whittling those down.