I've been informed that it is at least *theoretically* possible to point snapd to a only free "store" https://forum.snapcraft.io/t/external-repositories/1760/7
This might help us not have to remove snapd and then patch and maintain all the software that depends on snap and snapd.

This issue is not about what is acceptable for people hired by or representing Purism to do.

Although I agree that people at Purism shouldn't instruct how to install proprietary software, It would be difficult to forbid instructions or discussions about installing or upgrading Coreboot, which still contains blobs.

I am unaware of any issues with Firefox ESR violating the FSF Free System Distribution Guidelines.
We are aware of a some issues that might violate FSDG, and we are examining each of those individually.

I am unaware of any issues with Chromium violating the FSF Free System Distribution Guidelines.

The problem tracked in this issue is that you can install non-free packages or add non-free repos - including skype and others.
Which packages can most easily be installed due to the default configuration of the tool is a subset of this general issue.

The problem is not that you can install non-free packages or add non-free repos. So can you in apt. The problem is that snap is using Snapcraft repository by default. Just try snap find skype, snap find clion or snap find spotify.

Please note that this issue is about whether or not a package in PureOS is violating policies defined by Debian and/or FSF.

I wanted to add to this issue that Geogebra is no longer updated in Debian due to the license, cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692728. The problem is not only the documentation is licensed for non-commercial, but also the language files. As a result, it seems impossible to me to have a package with the free parts only, because such a version would not include any strings and hence be unusable?

What's the status on this? The issue of LibreJS is coming up again in general, and I will also be requesting some other addons are either default or opt-in (perhaps with a slide in the first-boot setup wizard for PureOS).

Done, hashcat 4.2.1-1 is in PureOS now.

yagf does not fallback-depend on a non-free package, only a non-existent one.

hashcat does not fallback-depend on a non-free package, only a non-existent one.

p7zip does not suggest a non-free package, only a non-existent one.

xarchiver does not suggest a non-free package, only a non-existent one.

It is a package manager. You can use it to install a .snap file (snap package) that you have downloaded by some other means, or that you have built yourself locally:

What is the purpose of snapd other than to download packages from external sources?

We better solver this independently from PureBrowser, to provide the freedom of opt-out to _not_ installing the plugin.

Either povray 1:3.7.0.4-2pureos1 went through NEW when I uploaded it on November 27 - three days _before_ your changes, or in went through NEW caused by your interventions.

The package went through NEW after I synchronized it with Debian, which leads to this situation now:
INFO: Can not sync povray: Target version '1:3.7.0.4-2pureos1' is newer/equal than source version '1:3.7.0.4-2'.
So, we can only properly sync this with Debian when the Debian version is newer (the archive will not allow downgrades).

Thanks for sharing!

I don't understand which timeline you are talking about.

This one was uploaded *after* I reverted the previous changes. Now I can't do that anymore without a fake upload, since the PureOS version is newer than in Debian.

@mak I believe you are the one orchestrating what constitutes "default install of PureOS".

This issue was originally reported as T108 but separated: We better solver this independently from PureBrowser, to provide the freedom of opt-out to _not_ installing the plugin.

This issue seems _not_ solved: Current povray package in PureOS green is 1:3.7.0.4-2pureos1 (the version which I explicitly requested to _drop_ as part of this issue).

Whoops, I forgot to close this...
The package has been force-synced with Debian and is now tracking Debian Testing again.

This is not a Freedom issue: It does not fallback-depend on any nonfree implementation but on the virtual package representing any implementation, so does not promote nonfree stuff (even at the stretched levels of suggesting or even mention).

Fixed by reporting upstream and fixing there.

Fixed package released - should reach green in 24 hours.