PureOS-project

pureos-project@lists.puri.sm

1 participants
104 discussions

Fedora removes MongoDB due to Server Side License issues
by Jeremiah C. Foster 16 Jan '19

16 Jan '19

Hi, Nicole shared with me this URL https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… from the Fedora mailing lists. TL;DR; is that the new MongoDB license is not considered "free" by Fedora and the question is if we ought to consider it non-free as well. I feel that Fedora's conclusion is not necessarily unreasonable. I do wonder what the impact might be but I suppose it might not be that large given the installed base of PureOS. It may affect Debian more if they decide they want to remove MongoDB. I do think there is another question though; how do we decide what stays in and what is kept out of PureOS? I feel we ought to curate our selection of packages from Debian given our limited resources for maintenance and since we're relying on Debian to do the type of license checking and curation that Fedora is doing. While I think that is reasonable given Debian's Free Software Guidelines it may not be appropriate. For example, what if Purism's Liberty services wants to use PureOS and they need MongoDB and have no problem with the license? Relying on Debian will not always meet our needs. This points the need for PureOS to be curated with regard to; - Licenses - Security - Fitness for purpose I think we'll need to try and come up with policies for each scope above, even if they end up being "we do what Debian does" or "we rely on Debian." The URL Nicole shared seems to be a good example of where PureOS policy might differ from our upstream. What is the view of folks here? Should we keep on including MongoDB or should we stop? Regards, Jeremiah

2 2

Re: [PureOS] Fedora removes MongoDB due to Server Side License issues
by Chris Lamb 16 Jan '19

16 Jan '19

Hi Jeremiah, > The URL Nicole shared seems to be a good example of where PureOS policy > might differ from our upstream. What is the view of folks here? My view is that our "upstream" is Debian, and unless I am missing something, we should just follow their lead here. As it happens, will almost-certainly mean its removal. See, the two Debian bugs in question: https://bugs.debian.org/915537 https://bugs.debian.org/916107 No need to write or curate policies until we see a need, a request or a lack of clarity, no? Best wishes, -- Chris Lamb https://puri.sm

2 1

Re: [Pureos-project] [Pureos-changes] Accepted gimp 2.8.22-1pureos1 (source all amd64) into landing
by Chris Lamb 10 Apr '18

10 Apr '18

Hi Jonas et al., > Source: gimp > Version: 2.8.22-1pureos1 […] > Changes: > gimp (2.8.22-1pureos1) green; urgency=medium > . > [ Chris Lamb ] > * Set the default UI layout to be "single window", disable the > creation of a floating toolbox, and create a dockable toolbox on > the left-hand side. Closes: PureOS:T266. I don't quite understand this part of the changelog entry. Surely the "single window mode" change was already in PureOS as part of my 2.8.20-1-pureos1 upload? (As an aside, a big part of *transparency* for PureOS outside world is not doing things that much differently to Debian, even if we can find some technical reasons for doing it. This has other advantages too, including reduceing any cognitive overhead when switching from work in Debian and/ or PureOS, as well as decreasing the bus factor & onboarding time of any new member of the team...) Best wishes, -- Chris Lamb https://puri.sm

1 0

[Pureos-project] Improvements to the PureOS lintian profile
by Chris Lamb 09 Apr '18

09 Apr '18

Hi, I've added some more features to Lintian in order to aid PureOS development. Specifically: + [CL] Add support for derivative-specific version validation to permit enforcement of additional restrictions on the version number such as being suffixed by "derivativeos1", etc. https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=425c2f8ef19e5… and: + [CL] Add support for derivative-specific field parsing to allow enforcement of additional restrictions (eg. updating Vcs-Git, etc.) https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=fb04da2937a68… I then added some PureOS-specific validation for these new features: + [CL] Ensure that PureOS packages always end with (eg. pureosX). + [CL] Add PureOS-specific field name validation, such as ensuring the Maintainer field is updated to the mailing list. ... which is resulting in errors (on a deliberately "broken" package) such as: $ lintian —profile=pureos /tmp/buildd/*.changes E: docbook-to-man changes: invalid-version-number-for-derivative 1:2.0.0-41 (must end with pureosX) E: docbook-to-man source: invalid-field-for-derivative maintainer: Chris Lamb <lamby(a)debian.org> (!= PureOS Maintainers <pureos-project(a)lists.puri.sm>) E: docbook-to-man source: invalid-field-for-derivative vcs-git: https://github.com/lamby/pkg-docbook-to-man.git (must point to code.puri.sm) E: docbook-to-man source: invalid-field-for-derivative vcs-browser: https://github.com/lamby/pkg-docbook-to-man (must point to code.puri.sm) Enjoy :) Best wishes, -- Chris Lamb https://puri.sm

1 0

2025

2024

2023

2022

2021

2020

2019

2018

PureOS-project