rinigus | piggz: yes, it is to keep the target clean. Otherwise I had some corner cases where the build was failing | 03:08 |
---|---|---|
T42 | <adampigg> Step 1, hybis-built! | 05:34 |
piggz | mal: gecko-dev still fails on a clean 4.1 target with that same weird python error for 486 .... | 05:44 |
piggz | how do you build it at jolla ??? | 05:44 |
piggz | mal: maybe some weird error with /dev/shm on the target? https://groups.google.com/g/ansible-devel/c/ns3nFcMpZPo?pli=1 | 07:20 |
mal | piggz: we just use OBS :) | 08:14 |
mal | not sure how people who develop it build it | 08:14 |
piggz | pretty sure i tried an obs build and struggled | 08:15 |
piggz | can try again | 08:15 |
piggz | from what i read, if i delete /dev/shm, python takes a different path and works | 08:15 |
piggz | but im not sure how to hde that from an sb2 targer | 08:15 |
mal | piggz: community OBS is a bit different | 08:16 |
piggz | sure ... maybe lbt can change that :D | 08:16 |
lbt | I'd like to upgrade the community OBS, yes | 08:20 |
lbt | ridiculously busy atm though | 08:20 |
Mister_Magister | lbt: it would be nice if jolla didn't delet community obs | 08:30 |
Mister_Magister | if i knew how to setup obs for sfos i would selfhost it xd | 08:30 |
lbt | it's quite a beast and we have a lot of changes so that's really tricky | 08:31 |
lbt | but I agree | 08:31 |
lbt | it's a bit catch-22 ... more use would be a good reason to keep it going - but since it's a bit neglected people don't use it too much | 08:31 |
lbt | It does have the latest SFOS on it and although aarch64 isn't working the rest is | 08:32 |
lbt | "use it or lose it" springs to mind | 08:32 |
Mister_Magister | i freaking love obs whether its opensuse or mer one | 08:33 |
Mister_Magister | hell you can put sfos obs as a sfos feature at this point | 08:33 |
lbt | (and yes, having announced a pending going away I can understand people being less interested in learning how to use it - gah!) | 08:33 |
Mister_Magister | lbt: because if its going away whats the point in doing something with it if its going to be deleted | 08:36 |
Mister_Magister | like… im not even planning on putting my hybris17 packages for 5z once i make them cause its gonn be deleted anyway | 08:36 |
Mister_Magister | lbt: would it be doable to idk plug in some jolla repos on opensuse's obs and build sfos packages on opensuse's obs that way? | 08:37 |
lbt | yeah - I know... and when I argue about it internally I get told no-one uses it and they've found alternatives... | 08:37 |
Mister_Magister | lbt: it really sucks | 08:37 |
lbt | no. we can't use suse | 08:37 |
Mister_Magister | why | 08:37 |
lbt | we use sb2 builds and they don't | 08:37 |
Mister_Magister | dang thats what i thought, but do we need sb2 | 08:37 |
Mister_Magister | like adding repos wouldn't be enough? | 08:38 |
lbt | realistically yes | 08:38 |
lbt | in fact categorically yes | 08:38 |
Mister_Magister | then whats the problem :P | 08:38 |
Mister_Magister | like for simple app building or device packages | 08:38 |
lbt | that was to "do we need sb2" | 08:38 |
Mister_Magister | ah | 08:38 |
Mister_Magister | why | 08:39 |
lbt | it's baked in - deeply | 08:39 |
* Mister_Magister lbt wrote over 6 years ago "webhooks for all" | 08:39 | |
lbt | hehe I remember, yes | 08:39 |
Mister_Magister | lbt: what do you mean? sb2 is just means of getting into arm chroot right | 08:39 |
lbt | "if you have to ask"... | 08:40 |
Mister_Magister | any vm/chroot would do | 08:40 |
Mister_Magister | like you can build the packages on device too | 08:40 |
Mister_Magister | like honestly when you use sb2 you just basically enter chroot so like any chroot with repos would do | 08:42 |
lbt | hehe ... yep. What would I know ? ;) | 08:42 |
Mister_Magister | lbt: nono, i'm just having hard time to understand | 08:42 |
Mister_Magister | i'm not saying you are wrong i just don't get it | 08:43 |
Mister_Magister | is there any significant difference in sb2 that makes us depend on it? | 08:43 |
lbt | when you dig into the whole build dependency and building the sb2 packages and cross-compiling is tightly integrated into the whole build system | 08:43 |
Mister_Magister | huuuuh | 08:44 |
lbt | of course you could fork the open spec files and rewrite - but that would no longer be SFOS and you'd be in a world of pain all by yourself ... it's just not viable | 08:44 |
Mister_Magister | hmmm | 08:45 |
lbt | sb2 cross-compiles arm by dropping out of the 'arm' qemu chroot to the underlying x86 and then spits arm binaries back up to qemu | 08:45 |
Mister_Magister | maybe you are takling about more internal/device specific packages needing sb2 | 08:45 |
Mister_Magister | huuh | 08:46 |
Mister_Magister | interesting | 08:46 |
Mister_Magister | but yeah loosing obs suuucks, you could even have CI from github for your apps and stuff | 08:47 |
Mister_Magister | lbt: i noticed decrease in workers over time :P | 08:48 |
lbt | yeah - machines dying and reducing costs | 08:48 |
Mister_Magister | but the "noone uses obs" confirms what i've been saying | 08:48 |
Mister_Magister | that noone uses/makes ports anymore | 08:48 |
lbt | yup - the move to openrepos way back meant that obs wasn't used/needed | 08:49 |
Mister_Magister | lbt: what do you mean? what move to openrepos | 08:49 |
piggz | lbt: how well do you know sb2? How could i remove /dev/shm from a target? | 08:52 |
lbt | piggz: quite well - but why? and what context | 08:53 |
Mister_Magister | lbt: how long are you in jolla | 08:53 |
lbt | since I was in Nokia working on Maemo - 2009 I think | 08:54 |
Mister_Magister | holy shit | 08:54 |
piggz | lbt: context is, the python configure script for configuring gecko-dev fails on an i486 target with this weird python error regargin semaphores https://paste.mozilla.org/eb7VjSS3 .... | 08:54 |
lbt | sdk ? | 08:54 |
Mister_Magister | the OG sailor before jolla even existed | 08:54 |
piggz | lbt: a sb2 target from the platform sdk | 08:55 |
piggz | lbt: i found some discussion around it being related to /dev/shm https://ask.csdn.net/questions/2948182 | 08:55 |
lbt | Mister_Magister: hehe - Carsten and I started Mer and showed Nokia how to use OBS to build an OS... the rest... | 08:55 |
piggz | and some other discussion that said if /dev/shm wasnt available, python would take a different path | 08:56 |
Mister_Magister | lbt: whoaaa | 08:56 |
lbt | piggz: yeah - so /dev/shm isn't working in sdk target? | 08:56 |
piggz | lbt: seems to | 08:56 |
piggz | s/so | 08:56 |
piggz | abranson: pointed me to this also https://git.sailfishos.org/mer-core/scratchbox2/commit/3fb3ee274234edac294aa6f700fcb6958b169216 | 08:56 |
lbt | that should be passed to the system's /dev/shm | 08:56 |
piggz | lbt: it is, but ls'ing it doesnt work | 08:56 |
Mister_Magister | lbt: but what do you mean "move to openrepos"? | 08:57 |
piggz | so, something weird is going on | 08:57 |
lbt | hmm - if abranson is stuck then... lessee | 08:57 |
piggz | on host: | 08:58 |
piggz | piggz@linux-f1uu ~ $ ls -lh /dev/shm | 08:58 |
piggz | total 8.0K | 08:58 |
piggz | -rw------- 1 piggz piggz 16 May 21 07:34 ELyjDx | 08:58 |
piggz | -rw------- 1 piggz piggz 16 May 21 08:40 s2uNjk | 08:58 |
piggz | [SB2 sdk-build SailfishOS-4.1.0.23-i486] piggz@linux-f1uu ~ $ ls -lh /dev/shm | 08:58 |
piggz | total 0 | 08:58 |
Mister_Magister | piggz: paste service | 08:58 |
Mister_Magister | >:( | 08:58 |
piggz | paste is for > 6 lines ;) | 08:58 |
Mister_Magister | not necessarily but fine | 08:58 |
* Mister_Magister i won't know what lbt meant with move to openrepos then | 09:01 | |
lbt | Mister_Magister: piggz: found it : https://git.sailfishos.org/mer-core/scratchbox2/tree/master/scratchbox2/docs | 09:07 |
lbt | the SB2_internals pdf | 09:07 |
Mister_Magister | nice | 09:07 |
Mister_Magister | would be worth reading if i wasn't dumb lazy fook | 09:08 |
Mister_Magister | just one document is over 10k words | 09:08 |
Mister_Magister | daaang | 09:08 |
lbt | Mister_Magister: then please don't waste my time asking why sb2 is needed | 09:08 |
Mister_Magister | >so why do we need sb2? | 09:08 |
Mister_Magister | >its complicated "10k word document" | 09:09 |
Mister_Magister | lbt: wow sorry then | 09:09 |
lbt | it's a pdf | 09:09 |
rinigus | in principle, suse obs can be used as they have arm64 builders (not qemu). in practice, unless they add SFOS to list of supported distros, not possible. | 09:09 |
rinigus | as users cannot add new OS as a "base" due to permissions | 09:10 |
lbt | rinigus: I doubt we qualify on license grounds - plus the spec and builds have sb2 hardcoded in too many places | 09:10 |
Mister_Magister | lbt: ohhhh so thats the reason | 09:10 |
rinigus | lbt: not sure about license if we use SFOS packages as provided by Jolla and build open source projects on top of it | 09:11 |
lbt | piggz: debugging your problem won't be easy | 09:11 |
rinigus | and in the packages that we build, don't think we have sb2 in spec. but I could be wrong | 09:11 |
lbt | how long does it take to hit it when you're in a build? | 09:11 |
lbt | rinigus: I mean to build sfos packages | 09:12 |
rinigus | ... long(ish). depends on architecture. arm32 bit - very long. arm64 bit could be fastest, but still would take packages | 09:12 |
rinigus | when you add any package. I was working against fedora | 09:13 |
piggz | lbt: its quick .. right at the configure step | 09:13 |
rinigus | so, suse obs is rather overused and hard to work with in practice | 09:13 |
lbt | piggz: OK - I'm thinking if you could give me a step-by-step to get to it so I can reproduce it quickly... | 09:13 |
lbt | then I can dig a little | 09:13 |
rinigus | lbt: as you chat with the both of us. license/sfos packages: you cannot build closed source components there. but it should be OK to build using them, assuming that suse will add SFOS to the list of distros | 09:15 |
lbt | piggz: I need to know which sdk you're using and then what to clone and what commands you run to get to a configure ... OK? | 09:15 |
Mister_Magister | rinigus: do you even need to add sfos to list of distros | 09:15 |
Mister_Magister | can't you just… add sfos repos | 09:16 |
Mister_Magister | to your repo config | 09:16 |
rinigus | now that they want to add closed source SFOS is probably not true and I don't think they will do it | 09:16 |
lbt | rinigus: our prjconf uses SB2 extensions to the OBS which simply won't work there | 09:16 |
piggz | lbt: this target: http://releases.sailfishos.org/sdk/targets/Sailfish_OS-4.1.0.23-Sailfish_SDK_Target-i486.tar.7z | 09:16 |
rinigus | Mister_Magister: yes, you need to do that. as users cannot add that type of external repositories | 09:16 |
Mister_Magister | ahhh gotcha | 09:16 |
piggz | lbt: this repo (will take a while to checkout!) https://git.sailfishos.org/mer-core/gecko-dev | 09:17 |
Mister_Magister | i really could selfhost obs but its more pain than actual usability | 09:17 |
lbt | piggz: how are you handling the rust side ? | 09:17 |
rinigus | Mister_Magister: I looked a bit into self-hosting and ended up writing tbuilder | 09:17 |
Mister_Magister | tbuilder? | 09:18 |
piggz | lbt: im not ... but im not getting that far! | 09:18 |
piggz | lbt: build works ok on the armv7hl target of the same version btw | 09:18 |
rinigus | Mister_Magister: https://github.com/rinigus/tbuilder ; port using it https://github.com/sailfishos-sony-tama/tbuilder-project | 09:19 |
Mister_Magister | rinigus: and what is that supposed to do? | 09:20 |
rinigus | lbt: what's prjconf? when working on nemo, I managed to build all packages from there on suse obs (using fedora as a base). haven't done closed source bits, as they are closed :) | 09:20 |
lbt | prjconf sets up the chroot essentially | 09:21 |
lbt | piggz: I didn't click - sb2 is not used for the 486 build at all | 09:22 |
rinigus | Mister_Magister: in nutshell - builds RPMs depending on each other. such as ports packages or complicated apps requiring many dependencies. | 09:22 |
rinigus | see spec and src in tbuilder project repo to get an idea what is built | 09:23 |
Mister_Magister | rinigus: huuh… why not… just run… build_packages.sh when its port | 09:23 |
Mister_Magister | and build app in sfossdk | 09:23 |
piggz | lbt: oh, so, how do i build on host? | 09:23 |
rinigus | Mister_Magister: hate to sit and wait for pressing enter or it failing somewhere in the middle. as for apps, maps stack requires so many libs that it is not funny to do it that way | 09:24 |
Mister_Magister | rinigus: gotcha | 09:24 |
rinigus | ... for same reasons you want to use OBS | 09:24 |
Mister_Magister | I will prably write some script for jenkins again | 09:25 |
rinigus | also, if you change one lib, it will also rebuild all other components that depend on it | 09:25 |
rinigus | as at obs | 09:25 |
Mister_Magister | i have script that builds zips already | 09:25 |
rinigus | lbt: OK, as nemo packages were building fine without it at suse obs, it is possible probably to build most of the parts there as well. except some closed source ones that rely on sb2 in spec. but, it is all irrelevant, I guess, as aarch64 hosts are probably much more expensive | 09:29 |
rinigus | in context of saving costs | 09:29 |
T42 | Mac %lastname% was added by: Mac %lastname% | 09:32 |
T42 | M %lastname% was added by: M %lastname% | 09:33 |
T42 | <M %lastname%> hello. Is any tama device porter available? | 09:33 |
Guest4137 | Is there a way to install SailfishOs on Samsung | 09:36 |
T42 | <edp_17> mighty17: I have checked my notes. Here it is how the BT started to work on my S2 (i9100): | 09:39 |
T42 | <edp_17> - I put the BT driver into kernel, not as module | 09:39 |
T42 | <edp_17> - created a file bcm4330b1.conf file into /etc/firmware/ | 09:39 |
T42 | <edp_17> - added file bluetooth-rfkill-event-hciattach into /etc/sysconfig/ | 09:39 |
T42 | <edp_17> - I checked the bt address and added into a file btmac into /etc/firmware/ | 09:39 |
T42 | <edp_17> - add file 100-bluetooth-brcm.rules into /lib/udev/rules.d/ | 09:39 |
T42 | <edp_17> Then I built broadcom-bluetooth and bluetooth-rfkill-event packages. All the files above can be found in my repo https://github.com/edp17/droid-config-i9100 | 09:39 |
T42 | <edp_17> @Guest4137: What Samsung device? | 09:40 |
Guest4137 | Samsung Galaxy S5 | 09:40 |
T42 | <edp_17> @Guest4137: I don't think SFOS is available for the S5. You can port it if you have time and the device with you. 😉 | 09:45 |
T42 | <ruspartisan> At least s5 has a lineageos 17.1 that you can build and run | 09:51 |
mighty17 | Thanks a lot @edp_17 i will do the same | 10:43 |
mighty17 | by BT driver u mean `CONFIG_BT_HCIUART_H4` right? | 10:44 |
mighty17 | @edp_17where did u get bt address? downstreamandroid? | 10:58 |
mighty17 | @edp_17 got the same error as u got during https://irclogs.sailfishos.org/logs/%23sailfishos-porters/%23sailfishos-porters.2020-06-05.log.html how did u fix it? | 11:18 |
mighty17 | i added the mr stuff in broadcom-bluetooth but idk about bluez-libs-devel | 11:18 |
T42 | <ruspartisan> I managed to boot pinephone image in qemu to show GUI, but I have a lot of messages in dmesg like "dbus-daemon[588]: dbus-daemon[588]: [session uid=100000 pid=588] Failed to activate service 'org.maliit.server': timed out (service_start_timeout=120000ms)" my quick google-fu shows that it's a virtual keyboard, but do I really need | 11:39 |
T42 | maliit if I plan to use external keyboard anyway? Can I just disable it? | 11:39 |
T42 | dumol was added by: dumol | 12:00 |
Mister_Magister | abff: abff | 13:14 |
*** wiktorek141 is now known as wiktorek140 | 13:44 | |
T42 | <adampigg> @ruspartisan [I managed to boot pinephone image in qemu to s …], Ah, good stuff | 14:05 |
*** abranson is now known as abr | 14:13 | |
T42 | <edp_17> @mighty17 [by BT driver u mean `CONFIG_BT_HCIUART_H4` rig …], Yes, CONFIG_BT_HCIUART_H4=Y | 15:03 |
T42 | <edp_17> @mighty17 [@edp_17where did u get bt address? downstreama …], BT address is from /efs/bluetooth/bt_addr | 15:04 |
T42 | <edp_17> @mighty17 [@edp_17 got the same error as u got during htt …], What error are you referring to? | 15:07 |
mighty17 | `bluez-libs-devel is needed by broadcom-bluetooth-1.0.4-1.armv7hl` @edp_17 | 16:30 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!