This is a meta-issue tracking a bundle of issues, and as such is not in itself a Freedom issue (that it identified for each unblundled issue). Lowering priority accordingly.

@adfeno I notice you mention lack of help examining, and also that you rely on licensecheck for your examination.

@EchedeyLR https://packages.debian.org/source/testing/chromium

In T57#14719, @jonas.smedegaard wrote:

@mak Please stop block chromium - it does not contain non-free code and is no longer unclear about licensing.

Also see https://directory.fsf.org/wiki/Review:Chromium-REV-ID-1 or https://directory.fsf.org/wiki/Talk:Chromium (the first link might be moved to the last one). Iridium Browser suffers from the same issues (this is described in the references). Also as described there, none of the lists is exhaustive, as we/volunteers from FSD lack some contributors specific for this issue.

@EchedeyLR Thanks for investigating. Please however report any concrete findings as separate issues.

I think there is still a similar problem with Chromium like https://tracker.pureos.net/T663 due to Google dependence/promotion.

In T57#14719, @jonas.smedegaard wrote:

@mak Please stop block chromium - it does not contain non-free code and is no longer unclear about licensing.

If I remember, Chromium is not packaged on Trisquel due to more problems but I am not sure.

@mak Please stop block chromium - it does not contain non-free code and is no longer unclear about licensing.

I don't think re-purposing this old bug for a blacklist removal request is a good idea - I was actually a bit confused to me to see seeing the bug appear again with this title...

This is no longer a freedom-issue, just cleanup internally...

Please drop blocking from Debian: Package has been dropped as obsolete now: See https://bugs.debian.org/874575

@zlatan.todoric LibreOffice build-depends on chromium, so this will be quite annoying.
Package is removed from PureOS now, but we will need to find a solution for LO...

@mak remove and block from re-entering the chromium package from archive as GNU-libre ML is pointing this out.

Changing status to "invalid", more appropriate for the task as a whole (arguably I should've created a subtask for the package removal which is indeed "done" by now).

Done

Please drop derived cron package: There is no need for deriving from Debian (issue is bogus).

This issue is bogus: It is correct for metadata to describe license as Artistic, but code itself is licensed "same as Perl" which means dual-licensing as _either_ Artistic or GPL-1+.

@mak Please block angband-doc from entering PureOS.

@mak please block simutrans, simutrans-pak128.britain, and simutrans-pak64,

@mak Ping!

test