Hi everyone,
A somber note today mostly to try to express solidarity for everyone on the list and anyone involved who may be going through hard times. Let me know personally if there's anything I can do.
With regard to PureOS it is onward and upward. Matthias has been working on integrating flatpak support into Laniakea. This is a big deal and I'm really excited to see it. We've been working on a CI pipeline that builds flatpaks and then they get uploaded to the CD system, but that has been problematic because a lot of the technolgy is new and it's shifted around a lot. Flatpaks also do a sort of nested virtualization or nested isolation and that can be difficult to handle with many of the tools we use. Having some native functionality in Laniakea will be very helpful.
I've been doing some poking at OpenQA from the SuSE folks. It is not packaged for Debian (though it's core package os-autoinst is). Trying to get a log in to Debian's instance of OpenQA https://openqa.debian.net/ leads to some weird site called microfocus.com. I wonder what relationship that holds to Debian's infrastructure? I'll have to dig a little more but I believe that having PureOS tested there might be a good thing. Kali is tested there as well so it may save us some disk space and CPU time to have it done there. We'll need to make sure that it meets the Free Software policies we have and while OpenQA itself surely does (its GPLv2), we shouldn't have to give info to a third party to access testing services.
The RYF application for the Librem Key is still in process. We've updated the source code and it's README and nearly completed our response to the FSF so hopefully we'll receive some good news when we resubmit.
That's it for now! Stay well and we'll get through this together!
Jeremiah
PS - I really mean it when I say you can reach out to me personally, I'm happy to talk to anyone on this list about PureOS, Purism, or just personal stuff.
-- Jeremiah C. Foster jeremiah.foster@puri.sm Gpg key id: 798DB834436A7BE38C97422D0DC062205451931B
Quoting Jeremiah C. Foster (2020-03-20 19:39:59)
I've been doing some poking at OpenQA from the SuSE folks. It is not packaged for Debian (though it's core package os-autoinst is). Trying to get a log in to Debian's instance of OpenQA https://openqa.debian.net/ leads to some weird site called microfocus.com. I wonder what relationship that holds to Debian's infrastructure?
The domain debian.org contains official Debian services, whereas debian.net contains services related to but not officially Debian.
I'll have to dig a little more but I believe that having PureOS tested there might be a good thing. Kali is tested there as well so it may save us some disk space and CPU time to have it done there. We'll need to make sure that it meets the Free Software policies we have and while OpenQA itself surely does (its GPLv2), we shouldn't have to give info to a third party to access testing services.
There are no such guarantees (from Debian, at least) for debian.net services, so you should consult whoever runs that service - and beware that it can change, so if you get guarantees from current provider then you should probably also setup some checks for the host shifting its provider.
- Jonas
On Fri, 2020-03-20 at 20:12 +0100, Jonas Smedegaard wrote:
Quoting Jeremiah C. Foster (2020-03-20 19:39:59)
I've been doing some poking at OpenQA from the SuSE folks. It is not packaged for Debian (though it's core package os-autoinst is). Trying to get a log in to Debian's instance of OpenQA https://openqa.debian.net/ leads to some weird site called microfocus.com. I wonder what relationship that holds to Debian's infrastructure?
The domain debian.org contains official Debian services, whereas debian.net contains services related to but not officially Debian.
Thanks Jonas - I completely missed that it was a *.net address.
I'll have to dig a little more but I believe that having PureOS tested there might be a good thing. Kali is tested there as well so it may save us some disk space and CPU time to have it done there. We'll need to make sure that it meets the Free Software policies we have and while OpenQA itself surely does (its GPLv2), we shouldn't have to give info to a third party to access testing services.
There are no such guarantees (from Debian, at least) for debian.net services, so you should consult whoever runs that service - and beware that it can change, so if you get guarantees from current provider then you should probably also setup some checks for the host shifting its provider.
Ah, okay. Thanks again!
Jeremiah
-
Jeremiah C. Foster -
Jonas Smedegaard