| rinigus | piggz: opened an issue https://forum.sailfishos.org/t/sb2-leads-to-faulty-qtwebengine-compilation/15296 | 05:41 |
|---|---|---|
| rinigus | in short, SB2 resulted in faulty compilation. I will try to tweak compilation (not sure if it will help), but we probably have to look for some better solution. see the issue and it would be good to voice the opinion there | 05:42 |
| b100dian[m] | An OBS build worker running on a raspberry? | 10:19 |
| rinigus | vlagged: no idea with how much ram and how powerful do they come these days. anything reasonable on where we can compile such codes is needed | 10:36 |
| rinigus | i/o maybe also an issue, in addition to cpu performance. probably some better alternatives are available | 10:44 |
| rinigus | however, after compilation on a phone, I wouldn't dismiss such an option. | 10:44 |
| x2s | mal: Finally I have some more logs for you | 16:32 |
| x2s | are there any privacy concerns with data from logcat outputs? | 16:32 |
| rinigus | piggz: I may have an idea that would work with SDK issue: make a docker image with sfos in corresponding arch. in contrast to coderus images, not to bundle any sdk into it, but just few minimal packages that can be used for a base config | 18:30 |
| rinigus | as if it is on device. tested with some very basic config and generated images using coderus baseimage's mic and it looks like it could work | 18:31 |
| rinigus | would have to see how to test aarch64. sounds like its possible | 18:32 |
| piggz | yes .... what aarch64 system would run it? | 18:32 |
| rinigus | start of the project at https://github.com/rinigus/docker-sailfishos-builder | 18:32 |
| rinigus | piggz: there are some CI providers with aarch64 | 18:33 |
| piggz | https://github.com/uraimo/run-on-arch-action | 18:33 |
| piggz | some github action too | 18:33 |
| rinigus | I think those were non-native | 18:33 |
| rinigus | piggz: https://buildjet.com/for-github-actions/pricing with arm | 18:35 |
| rinigus | so, if it works out, we can build some huge packages there and then upload results to obs. as we do with some of hybris packages | 18:36 |
| piggz | sure | 18:36 |
| piggz | i wonder, would the gitlab in qemu work fine anyway? its atleast 64 bit | 18:36 |
| rinigus | piggz: it probably would. just ... ... s.l.o..w. but let's see | 18:41 |
| piggz | rinigus: i wonder if the pinephone rootfs could be useful | 18:41 |
| rinigus | piggz: could be. looking through tama KS to see which packages to include. we basically have to fill https://github.com/rinigus/docker-sailfishos-builder/blob/main/base.ks packages section | 18:43 |
| rinigus | I wonder which package creates defaultuser? | 18:44 |
| rinigus | somehow feels wrong to compile under root | 18:44 |
| piggz | i have a feeling its a startup script these days ... mal might know? | 18:45 |
| mal | piggz: ? | 18:46 |
| piggz | mal: what created defaultuser? | 18:47 |
| mal | I think something during boot, not sure exactly what | 18:49 |
| rinigus | could be, as we have encryption setup as well. OK, no problem - I can create user while building it | 18:51 |
| mal | rinigus: piggz: /usr/lib/startup/start-autologin | 18:51 |
| rinigus | mal: thanks. it makes sense for me to just create it with useradd | 18:53 |
| mal | yeah, somewhere in image build post part | 18:55 |
| piggz | rinigus: in the pine and halium images, i already do a bunch of groupadd type stuff for things that the hybris packages do | 18:56 |
| piggz | rinigus: https://gitlab.com/sailfishos-porters-ci/dont_be_evil-ci/-/blob/master/pinephonepro/Jolla-%40RELEASE%40-pinephonepro-%40ARCH%40.ks#L124 | 18:58 |
| rinigus | piggz: I will try to do it inside Dockerfile. there are few things we need to specify there anyway... | 18:59 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!