@jonas.smedegaard I can not block binary packages, it's either all or nothing. You will need to edit the package in PureOS, removing the problematic pieces.
Only syncing a few binary packages leads to an inconsistent archive with big headaches for QA, and if we later rebuild all packages from scratch becomes completely impossible.
So, adding a PureOS delta is the way to go here.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Oct 7 2017
This has been blacklisted for ages now :-)
Oct 5 2017
@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.
Oct 3 2017
Kodi was removed from Debian testing some time ago due to FTBFS with GCC7.
Sep 18 2017
Dropped from Debian testing (and consequently from PureOS), and unlikely to reappear without addressing the bug.
Fixed in Debian.
Sep 14 2017
(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.
Is it that the programs sent by the individual projects for the clients to calculate are often nonfree?
Sep 10 2017
adding @theodotos.andreou so he knows about the need of service similar to debian.net subdomain. Coordinate that together.
Sep 9 2017
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).
no, by default things without license are considered proprietary unless someone did investigation and put it in pd if it suits that. If you want you could try contact authors of those addons and ask them to specify license
Yes, but if a plugin does not have a license tag, can we consider it public domain?
Not sure what you are asking.
What about those which don't have license field?
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.
Sep 7 2017
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.
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.
Removed from Debian testing (for different reason, but expected to not re-enter without addressing this bug first).
Sep 4 2017
Bug reported to Debian.
Aug 22 2017
Fixed hydrogen entered testing today.