Andres On Friday, March 17, 2023 6:11:04 PM MST Andres Salomon wrote: > Right, and debian's chromium is still carrying around a patch that > works around that older problematic unicode license. I've been meaning > to drop that patch.
Currently, Lintian will flag any Convert-UTF file as a problem, even if it has the newer license. However, once the following MR is merged into Lintian, then it will no longer produce false positives. https://salsa.debian.org/lintian/lintian/-/merge_requests/461[1] > Where are you seeing this? > > dilinger@hm90:~$ grep -i "Unicode St" > sid-build/chromium-111.0.5563.64/third_party/icu/source/data/mappings/iso-88 > 59_1* ; echo $? > 1 > dilinger@hm90:~$ head -n2 > sid-build/chromium-111.0.5563.64/third_party/icu/source/data/mappings/iso-88 > 59_10-1998.ucm # Copyright (C) 2016 and later: Unicode, Inc. and others. > # License & terms of use: http://www.unicode.org/copyright.html It turns out that this has already been fixed sometimes between Chromium 108 and Chromium 111. https://sources.debian.org/src/chromium/108.0.5359.94-1~deb11u1/third_party/icu/source/ data/mappings/iso-8859_10-1998.ucm/[2] https://sources.debian.org/src/chromium/111.0.5563.64-1/third_party/icu/source/data/ mappings/iso-8859_10-1998.ucm/[3] After patching Lintian with a test that correctly found these files I ran it against a bunch of packages I had already built on my system. The version of the Chromium package I had around was 108, and I didn’t imagine that anything had changed in this regard since then. Turns our that assumption was incorrect. > Chromium's git repo doesn't include a bunch of third_party stuff; that > stuff gets pulled in automatically when the chromium devs generate > release tarballs. The directory in the release tarball documents where > they originate. In this case, in third_party/icu/README.chromium . > According to that, the source is from > https://github.com/unicode-org/icu . Even though I thought that repository had been updated in 2015, it looks like those particular licenses were only fixed in the repository in April 2022. Which explains the Chromium 108/111 difference. > > with the license at: > Yeah, breakpad's LICENSE file needs to be corrected. I can send a patch > upstream for that. Thanks. -- Soren Stoutner so...@stoutner.com --------
signature.asc
Description: This is a digitally signed message part.
