Friday, 2021-05-21

riniguspiggz: yes, it is to keep the target clean. Otherwise I had some corner cases where the build was failing03:08
T42<adampigg> Step 1, hybis-built!05:34
piggzmal: gecko-dev still fails on a clean 4.1 target with that same weird python error for 486 ....05:44
piggzhow do you build it at jolla ???05:44
piggzmal: maybe some weird error with /dev/shm on the target?
malpiggz: we just use OBS :)08:14
malnot sure how people who develop it build it08:14
piggzpretty sure i tried an obs build and struggled08:15
piggzcan try again08:15
piggzfrom what i read, if i delete /dev/shm, python takes a different path and works08:15
piggzbut im not sure how to hde that from an sb2 targer08:15
malpiggz: community OBS is a bit different08:16
piggzsure ... maybe lbt can change that :D08:16
lbtI'd like to upgrade the community OBS, yes08:20
lbtridiculously busy atm though08:20
Mister_Magisterlbt: it would be nice if jolla didn't delet community obs08:30
Mister_Magisterif i knew how to setup obs for sfos i would selfhost it xd08:30
lbtit's quite a beast and we have a lot of changes so that's really tricky08:31
lbtbut I agree08:31
lbtit'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 much08:31
lbtIt does have the latest SFOS on it and although aarch64 isn't working the rest is08:32
lbt"use it or lose it" springs to mind08:32
Mister_Magisteri freaking love obs whether its opensuse or mer one08:33
Mister_Magisterhell you can put sfos obs as a sfos feature at this point08: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_Magisterlbt: because if its going away whats the point in doing something with it if its going to be deleted08:36
Mister_Magisterlike… im not even planning on putting my hybris17 packages for 5z once i make them cause its gonn be deleted anyway08:36
Mister_Magisterlbt: 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
lbtyeah - I know... and when I argue about it internally I get told no-one uses it and they've found alternatives...08:37
Mister_Magisterlbt: it really sucks08:37
lbtno. we can't use suse08:37
lbtwe use sb2 builds and they don't08:37
Mister_Magisterdang thats what i thought, but do we need sb208:37
Mister_Magisterlike adding repos wouldn't be enough?08:38
lbtrealistically yes08:38
lbtin fact categorically yes08:38
Mister_Magisterthen whats the problem :P08:38
Mister_Magisterlike for simple app building or device packages08:38
lbtthat was to "do we need sb2"08:38
lbtit's baked in - deeply08:39
* Mister_Magister lbt wrote over 6 years ago "webhooks for all"08:39
lbthehe I remember, yes08:39
Mister_Magisterlbt: what do you mean? sb2 is just means of getting into arm chroot right08:39
lbt"if you have to ask"...08:40
Mister_Magisterany vm/chroot would do08:40
Mister_Magisterlike you can build the packages on device too08:40
Mister_Magisterlike honestly when you use sb2 you just basically enter chroot so like any chroot with repos would do08:42
lbthehe ... yep. What would I know ? ;)08:42
Mister_Magisterlbt: nono, i'm just having hard time to understand08:42
Mister_Magisteri'm not saying you are wrong i just don't get it08:43
Mister_Magisteris there any significant difference in sb2 that makes us depend on it?08:43
lbtwhen you dig into the whole build dependency and building the sb2 packages and cross-compiling is tightly integrated into the whole build system08:43
lbtof 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 viable08:44
lbtsb2 cross-compiles arm by dropping out of the 'arm' qemu chroot to the underlying x86 and then spits arm binaries back up to qemu08:45
Mister_Magistermaybe you are takling about more internal/device specific packages needing sb208:45
Mister_Magisterbut yeah loosing obs suuucks, you could even have CI from github for your apps and stuff08:47
Mister_Magisterlbt: i noticed decrease in workers over time :P08:48
lbtyeah - machines dying and reducing costs08:48
Mister_Magisterbut the "noone uses obs" confirms what i've been saying08:48
Mister_Magisterthat noone uses/makes ports anymore08:48
lbtyup - the move to openrepos way back meant that obs wasn't used/needed08:49
Mister_Magisterlbt: what do you mean? what move to openrepos08:49
piggzlbt: how well do you know sb2? How could i remove /dev/shm from a target?08:52
lbtpiggz: quite well - but why? and what context08:53
Mister_Magisterlbt: how long are you in jolla08:53
lbtsince I was in Nokia working on Maemo - 2009 I think08:54
Mister_Magisterholy shit08:54
piggzlbt: context is, the python configure script for configuring gecko-dev fails on an i486 target with this weird python error regargin semaphores ....08:54
lbtsdk ?08:54
Mister_Magisterthe OG sailor before jolla even existed08:54
piggzlbt: a sb2 target from the platform sdk08:55
piggzlbt: i found some discussion around it being related to /dev/shm
lbtMister_Magister: hehe - Carsten and I started Mer and showed Nokia how to use OBS to build an OS... the rest...08:55
piggzand some other discussion that said if /dev/shm wasnt available, python would take a different path08:56
Mister_Magisterlbt: whoaaa08:56
lbtpiggz: yeah - so /dev/shm isn't working in sdk target?08:56
piggzlbt: seems to08:56
piggzabranson: pointed me to this also
lbtthat should be passed to the system's /dev/shm08:56
piggzlbt: it is, but ls'ing it doesnt work08:56
Mister_Magisterlbt: but what do you mean "move to openrepos"?08:57
piggzso, something weird is going on08:57
lbthmm - if abranson is stuck then... lessee08:57
piggzon host:08:58
piggzpiggz@linux-f1uu ~ $ ls -lh /dev/shm08:58
piggztotal 8.0K08:58
piggz-rw------- 1 piggz piggz 16 May 21 07:34 ELyjDx08:58
piggz-rw------- 1 piggz piggz 16 May 21 08:40 s2uNjk08:58
piggz[SB2 sdk-build SailfishOS-] piggz@linux-f1uu ~ $ ls -lh /dev/shm08:58
piggztotal 008:58
Mister_Magisterpiggz: paste service08:58
piggzpaste is for > 6 lines ;)08:58
Mister_Magisternot necessarily but fine08:58
* Mister_Magister i won't know what lbt meant with move to openrepos then09:01
lbtMister_Magister:  piggz: found it :
lbtthe SB2_internals pdf09:07
Mister_Magisterwould be worth reading if i wasn't dumb lazy fook09:08
Mister_Magisterjust one document is over 10k words09:08
lbtMister_Magister: then please don't waste my time asking why sb2 is needed09:08
Mister_Magister>so why do we need sb2?09:08
Mister_Magister>its complicated "10k word document"09:09
Mister_Magisterlbt: wow sorry then09:09
lbtit's a pdf09:09
rinigusin 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
rinigusas users cannot add new OS as a "base" due to permissions09:10
lbtrinigus: I doubt we qualify on license grounds - plus the spec and builds have sb2 hardcoded in too many places09:10
Mister_Magisterlbt: ohhhh so thats the reason09:10
riniguslbt: not sure about license if we use SFOS packages as provided by Jolla and build open source projects on top of it09:11
lbtpiggz: debugging your problem won't be easy09:11
rinigusand in the packages that we build, don't think we have sb2 in spec. but I could be wrong09:11
lbthow long does it take to hit it when you're in a build?09:11
lbtrinigus: I mean to build sfos packages09:12
rinigus... long(ish). depends on architecture. arm32 bit - very long. arm64 bit could be fastest, but still would take packages09:12
riniguswhen you add any package. I was working against fedora09:13
piggzlbt: its quick .. right at the configure step09:13
rinigusso, suse obs is rather overused and hard to work with in practice09:13
lbtpiggz: 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
lbtthen I can dig a little09:13
riniguslbt: 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 distros09:15
lbtpiggz: 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_Magisterrinigus: do you even need to add sfos to list of distros09:15
Mister_Magistercan't you just… add sfos repos09:16
Mister_Magisterto your repo config09:16
rinigusnow that they want to add closed source SFOS is probably not true and I don't think they will do it09:16
lbtrinigus: our prjconf uses SB2 extensions to the OBS which simply won't work there09:16
piggzlbt: this target:
rinigusMister_Magister: yes, you need to do that. as users cannot add that type of external repositories09:16
Mister_Magisterahhh gotcha09:16
piggzlbt: this repo (will take a while to checkout!)
Mister_Magisteri really could selfhost obs but its more pain than actual usability09:17
lbtpiggz: how are you handling the rust side ?09:17
rinigusMister_Magister: I looked a bit into self-hosting and ended up writing tbuilder09:17
piggzlbt: im not ... but im not getting that far!09:18
piggzlbt: build works ok on the armv7hl target of the same version btw09:18
rinigusMister_Magister: ; port using it
Mister_Magisterrinigus: and what is that supposed to do?09:20
riniguslbt: 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
lbtprjconf sets up the chroot essentially09:21
lbtpiggz: I didn't click - sb2 is not used for the 486 build at all09:22
rinigusMister_Magister: in nutshell - builds RPMs depending on each other. such as ports packages or complicated apps requiring many dependencies.09:22
rinigussee spec and src in tbuilder project repo to get an idea what is built09:23
Mister_Magisterrinigus: huuh… why not… just run… when its port09:23
Mister_Magisterand build app in sfossdk09:23
piggzlbt: oh, so, how do i build on host?09:23
rinigusMister_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 way09:24
Mister_Magisterrinigus: gotcha09:24
rinigus... for same reasons you want to use OBS09:24
Mister_MagisterI will prably write some script for jenkins again09:25
rinigusalso, if you change one lib, it will also rebuild all other components that depend on it09:25
rinigusas at obs09:25
Mister_Magisteri have script that builds zips already09:25
riniguslbt: 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 expensive09:29
rinigusin context of saving costs09:29
T42Mac %lastname% was added by: Mac %lastname%09:32
T42M %lastname% was added by: M %lastname%09:33
T42<M %lastname%> hello. Is any tama device porter available?09:33
Guest4137Is there a way to install SailfishOs on Samsung09: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 module09: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
T42<edp_17> @Guest4137: What Samsung device?09:40
Guest4137Samsung Galaxy S509: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 run09:51
mighty17Thanks a lot @edp_17 i will do the same10:43
mighty17by 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 how did u fix it?11:18
mighty17i added the mr stuff in broadcom-bluetooth but idk about bluez-libs-devel11: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 need11:39
T42maliit if I plan to use external keyboard anyway? Can I just disable it?11:39
T42dumol was added by: dumol12:00
Mister_Magisterabff: abff13:14
*** wiktorek141 is now known as wiktorek14013:44
T42<adampigg> @ruspartisan [I managed to boot pinephone image in qemu to s …], Ah, good stuff14:05
*** abranson is now known as abr14:13
T42<edp_17> @mighty17 [by BT driver u mean `CONFIG_BT_HCIUART_H4` rig …], Yes, CONFIG_BT_HCIUART_H4=Y15:03
T42<edp_17> @mighty17 [@edp_17where did u get bt address? downstreama …], BT address is from /efs/bluetooth/bt_addr15: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_1716:30

Generated by 2.17.1 by Marius Gedminas - find it at!