Fixed since Debian release 2.4-3 in 2010.

Parabola build routines declares individual docx source files as additional sources in its rpms metadata.

This bug is bogus: Parabola patch do not avoid any promotion of non-free stuff, only refences to Free stuff by (arguably non-free trademark-protected) labels.

While true that smtube _can_ use tonvid.com, Debian distribution of smtube does not.

bogusly forked fromT61: It is tonvid.com (not smtube itslef) that tracks users.

Current status:

I dput'ed last night a fork of Debian kodi, stripped of the kodi-repository-kodi binary package.

for the record:

Ok. Thanks for the explanation.

Ignore: I misunderstood how this rolling release of PureOS should _not_ auto-remove what gets removed from Debian testing.

@mak can you block (not src:kodi but) the binary package kodi-repository-kodi from entering PureOS?

Debian kodi package re-entered unstable today, which means it will re-enter likely re-enter PureOS 10 days from now.

Debian kodi package re-entered unstable today, which means it will likely re-enter PureOS 10 days from now.

Kodi was removed from Debian testing some time ago due to FTBFS with GCC7.

Dropped from Debian testing (and consequently from PureOS), and unlikely to reappear without addressing the bug.

Fixed in Debian.

(as a sidenote I also realize that a web browser can execute code from alien sources and similarly cannot be ensured to only process Freely licensed code - I have no idea by which logic FSF can approve operating systems containing web browsers...)

I don't understand BOINC well enough to say how exactly the distributed code gets fed into the system, only (believe that I) understand that it does happen and that we cannot ensure that code fed into the system is freely licensed.

Plan: Establish a web service as a debian.net subdomain:

In most of the World, copyright is automatic (i.e. there is an implicit "all rights reserved"), and as a consequence licensing must be explicit too (and arguably copyright statement must be explicit too, to be able to validate if the licensing was granted by the copyright holder and not bogusly from someone else not in possesion of rights granted).

Not sure what you are asking.

Upstream repository feed:

More sustainable than subscribing to a non-default repository - whether maintained by us or picking a third-party repository - is to setup a proxy for the feed which filters the repository feed and lets through only those with a license known to be Free.

Parabola patch is therefore overzealous: Only the three lines changing URL are relevant.

Parabola issue 1035 really tracks two different issues: a) contains non-free decompression engine for RAR archives, and b) support for non-free addons.

I agree with the conclusion done by Trisquel: While Debian arguably tolerate Free clients pulling non-free code from external services, PureOS cannot do that when seeking FSF endorsement.

Debian package does a fair job of stripping non-free sources, including the convenience code copy of glut code.

Upstream is dead, and alternatives exist. Seems just a matter of time before it is dropped in Debian.

Only Matthias can block packages.

GeoGebra licenses its documentation as CC-BY-SA-3.0, since at least version 3.2.40.0 packaged prior to initial release in Debian in 2010.

As I understand it, QTox is different from Matrix:

oh well - it _is_ browser agnostic already (se Debian bugreport).

copyright referenced at the Github page seems to not cover documentation, and also what seems to be copyright portected in the documentation package is only the _packaging_ of it: Manoj is a Debian developer, and at least none of the few documentation files I randomly looked at were authored by Manoj.

Bogus issue: Does not affect freedoms.

I recommend *against* pulling in third-party code repositories.

This recent Debian thread looks related: http://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2017-September/020574.html

Better to be browser-agnostic by use of xdg-open

Both cups-filters and inkscape recommend imagemagick.

Removed from Debian testing (for different reason, but expected to not re-enter without addressing this bug first).

Bug reported to Debian.

for inspiration, have a look at which packages gets pulled in by the Debian package parl-desktop-world. Creation and maintenance of that package revealed buggy naming of some dictionaries and conflicts between others, indicating to me that "full coverage" was perhaps never explored in Debian until then.

Where is the source package selection for the default install of PureOS located? I can take a look at identifying addon packages needed for worldwide coverage (as much as we have it available in Debian), to see how much additional space that would require.