[PureOS] PureOS Phone images

Jeremiah C. Foster jeremiah.foster at puri.sm
Thu Aug 27 19:29:04 PDT 2020


[Feel free to reply on-list, I just wanted to make sure everyone saw

[Please find attached an invite to a mumble call at 16:00 CEST

Welcome to a thread about PureOS images for our Librem 5 phone. 

Let's start with Guido who knows a thing or two about the Librem 5;

"I'd like to (slowly) start filling in enough of byzantium so we can
build images for the phone. First candidates would be a kernel and
flash-kernel. We currently keep the sources at 
https://source.puri.sm/Librem5/flash-kernel and 
https://source.puri.sm/Librem5/linux-next - i just wanted to check that
there aren't any objections when the number of packages with patches
increases quite a bit."

Matthias writes;
"First of all, thank you for communicating this early :-) I have no
fundamental objections to adding it, you would just need to target
"byzantium" or "landing". 

- Any chance that the kernel changes would break the desktop flavor of
PureOS? Or would that be a completely separate kernel package and not
merged with the desktop kernel?

- You'd need to make sure phone things work on amd64 as well as on
arm64 in case they have a convergent base and are used on both form
factors. And 3) the PureOS team is tiny so we can't maintain lots and
lots of PureOS<->Debian delta. But with the phone team's help I think
that's absolutely doable there's also secondary questions, like whether
it makes sense to just move shared sources to the pureos group(s) in
Gitlab also, I'll have to go through with improving Laniakea's sync
overview page to be less cluttered - at the moment it's quite hard to
know what needs merging where ;-) (that's actually the thing I am
working on at the moment, since that also gets rid of the last bit of D
code and makes deploying Laniakea easier).

- Laniakea can theoretically also build packages from Git repos -
you'll need a list of repos and signed tags of a certain format in
them, LK will then verify the tag signature and send the repo to a
worker to create a source package out of that's then auto-uploaded.
It's quite neat in concept...

....in practice I would need to get rid of the manual list and actually
verify signatures (at the moment anything would be built, so that's
really not deployable)

Anyway, that's $future_stuff, let's work on getting the phone pieces
into byzantium easily first :-)"

Jeremiah writes;
- I would like to understand more about the increase in kernel patches;
how will they be maintained? What are the expectations of the Librem 5
team, is there going to be a transfer of responsibility for the patches
from the Librem 5 team to PureOS team?

Our resources are currently thinly stretched across our CI / CD, QA,
and support teams, which means adding devices is a heavy lift that
needs co-ordination. We don't really have a process for additional
devices yet either and there needs to be some thought as we grow given
that our Librem 5 traffic might significantly increase load and
bandwidth on existing infrastructure. Do we have any data on;

- Currently Librem 5 CI (I believe we run Munin on the ARM 02 server
no? Do we have output from that which might show load, disk, CPU, etc?

- How about the current instance of Laniakea? Are we running Munin? If
not, do we have data on the server from a capacity planning standpoint?

- I'd like to know a bit more about the plan - do we intend to use your
new process to build from git repos with signed tags Matthias? Or are
we going to continue to build on ARM 02 and then upload to Laniakea?

Best regards,

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puri.sm/pipermail/pureos-project/attachments/20200827/4d4d815d/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Nextcloud-0J6XOJ7LSV5RW8VYMMZSEV.ics
Type: text/calendar
Size: 1864 bytes
Desc: not available
URL: <http://lists.puri.sm/pipermail/pureos-project/attachments/20200827/4d4d815d/attachment.ics>

More information about the PureOS-project mailing list