[Debian-on-mobile-maintainers] Fwd: Your package buffybox

[undef]

Hi,

On 12/31/25 20:42, Mechtilde Stehmann wrote:
> Hello, 
<snip>
> The problem is the content of "lvgl/docs/CONTRIBUTING.rst:220 f." and 
> "lvgl/LICENCE.txt" in the lvgl directory.


I've had a talk to another developer working on Mobian/Debian to try to 
clarify this. We both believe that the key point of confusion is that 
this package contains two different projects:

 1. LVGL: A vendored graphics library.
 2. Buffybox: The project I'm actually trying to package.

As such, there are two different upstreams, with two different license 
policies:

 1. LVGL: This project quite reasonably doesn't accept GPL-only code to
    allow the library as a whole to remain MIT.
 2. Buffybox: This project includes some MIT code from LVGL, but is not
    required to follow the contibuting guide for LVGL.

This is made a fair bit more obvious in the upstream repo 
(https://gitlab.postmarketos.org/postmarketOS/buffybox) where LVGL is a 
git submodule. They are packaged as a single upstream tarball simply to 
provide an easier experience with uscan v4.


>
>
>> Additionally, regarding the MIT license information being missing, 
>> I'd previously been told that "Expat" should be used rather than 
>> "MIT" in debian/copyright [0]. If this is incorrect I'm more than 
>> happy to change it. I believe the license holders for the MIT code 
>> are correctly covered when considering MIT and Expat as the same.
>
> Yes the text of the MIT license shipped by upstream is the same than 
> in the publish Expat license.
>
> Please forward the issue to upstream with the above text "LVGL can not 
> accept GPL licensed code" regarding the compatibility of GPL and MIT. 
> Both license are used in the same package.


Because of the above description of two different upstreams, I don't 
believe it would be reasonable to ask LVGL to remove this comment.

>
> The new DFSG team is still waiting to be able to release the package 
> into the Debian archive.
> You can use this time to clarify the aforementioned license issue with 
> upstream. You can also perform the update into the New Queue.


I am currently preparing a new version of the package with a few license 
issues ironed out and the latest upstream release. I will also include a 
readme.Debian file explaining the two upstreams and their relationship.


Thanks,

Undef.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/debian-on-mobile-maintainers/attachments/20260102/23e45a77/attachment.htm>