- User Since
- Oct 15 2016, 3:53 PM (143 w, 5 d)
Jun 19 2018
Purism branding elements can be packaged in the repositories of both the normal and OEM versions of PureOS, but preinstalled (or activated) only in the OEM version (i.e. so that the "purism-branding" package is installed by default on factory-preloaded Librem devices, but not on non-purism devices where people install PureOS themselves).
Apr 24 2018
Jan 26 2018
NetworkManager has a provision for this, and it gets exposed in the WiFi connection preferences in nm-connection-editor, but IIRC:
Jan 1 2018
Oct 9 2017
Oct 3 2017
Pardon my silly question, but as the latest release of Firefox ESR is version 52.4, could we take the opportunity to leap to that instead of being stuck at the 1.5-years-old 45 series, and lock ourselves into version 52 for the foreseeable future? (I would tend to think we should not jump to regular Firefox 57+ for a while, because the forceful migration to webextensions might cause us untold misery)
Jul 25 2017
Jul 24 2017
Apparently not fixed as you still get the same issue after applying the latest updates.
Jul 15 2017
I "fixed" the issue by removing that row. I was previously hoping to make a new version of that file, but this is clearly not happening and I don't see much point in a PDF spec sheet vs the live-updated products comparison table anyway, so I just removed it now.
Jun 13 2017
May 23 2017
Over the years I've had all the creative apps (Inkscape, GIMP, Krita, Scribus, Blender, MyPaint, Calligra, etc.) installed and I never saw ImageMagick installed, I didn't even know a GUI existed for it ;) so given that PureOS3 beta doesn't have any creative apps preinstalled, I don't see where this thing appeared from.
May 22 2017
Confirming that with the beta, applying updates in gnome software caused no problem.
May 21 2017
@zlatan.todoric Well having a command line to give to people is the workaround until we have the real solution: exposing locale packages in GNOME Software and/or allowing gnome-control-center to install them as needed. Low priority given that we have a workaround, but this is is something that would be expected nonetheless to give a good user experience.
May 9 2017
Apr 18 2017
That's the "optimal solution"; in the meantime, if it is not a quick-and-trivial thing to implement in Debian, I would like us to at least have a way to tell users how to install the relevant packages for their locale with one simple command (ie how to figure out the correct package names), in case anybody asks @mladen.pejakovic