On Fri, Jun 14, 2024 at 9:29 AM Alexandre Rossi <n...@zincube.net> wrote: > Regarding those valid points, because there is not reason to have the same > source in multiple packages, there are only 2 paths compliant with the Debian > policy: > > 1) Fix those points in src:libb64 for transmission and all rdepends > 2) Remove src:libb64 from Debian and then vendor in transmission source > > I'll try to move towards 1) and see how it goes. So for now, this is a > wontfix because against DFSG.
I agree that it would be helpful if many of these issues were fixed for all users of libb64. On the other hand, this does not fix the fact that libb64 has been unmaintained since 2013 and therefore it still wouldn't be a good candidate to complete Ubuntu's Main Inclusion process even if the other issues were fixed. Therefore, Ubuntu will need to keep vendoring libb64 in transmission. I am unaware of any maintained version of libb64. I disagree that this violates the Debian Free Software Guidelines although it does violate what is normally considered "best practice" in Debian development. However, there are many exceptions to this best practice in Debian and there is a lot of vendored code. (Even after your recent work, transmission still has vendored code and that is not a DFSG violation). Notably, Debian ftpmasters routinely accept new packages that have vendored code as long as the code is correctly documented in debian/copyright (which had been done for transmission). See https://wiki.debian.org/EmbeddedCopies Thank you, Jeremy Bícha
