Wednesday, 2026-07-15

*** n2klb_ is now known as n2klb02:01
riniguspiggz & nephros : qt6-webengine is available now for 5.1. angelfish was compiled for 5.1 as well, so its ready for testing. haven't tried myself - I'm on 5.0 still.10:57
piggz[m]amazing10:57
piggz[m]im on 5.2 though :D10:58
rinigusI do wonder, if we should switch chum to "new-non-tested" sb2. in a same manner as we have for your qt6 repos. that way we can at least test it on rather large software library. and it will allow us to move all qt6 to chum and chum:testing11:09
piggz[m]yes, i wonder that too ... maybe mal/keto can advise how far the sb3 change is from being merged?11:37
rinigusas we can "hide" sb2 from distribution, it would impact compilation only. and should be useful for mal or someone else reviewing this PR. but for that, we would need to record all successful chum packages and see if it changes after sb2 switch11:45
Ketoat the moment the plan is to have it in 5.3. due to pressure on getting the new device working we did not push it to 5.2 in order to avoid any extra issues11:51
Ketoand to keep things simple we have the 5.2 release branch still following the "live" devel, to avoid the need to push changes in two branches, so we have not merged th sb2 changes yet11:54
piggz[m]whak is the (currently) expected timeframe for 5.3?11:56
piggz[m]i know you dont give times, but indicative?11:56
Ketobut as soon as things stabilize a bit, we'll detach the 5.2 branch and can take those bigger things in11:56
Ketomy guess for the timeline at the moment is maybe later this year :)11:59
piggz[m]:/12:02
rinigusso, it will take a while. I don't think we need to link it to specific SFOS release as, in theory, sb2 changes should not have any impact on compiled code. so, my suggestion to start compiling 5.1 and maybe few other versions for chum using "new" sb2 stands :) . just look into forum thread on angelfish and what users do to enable piggz repos - its a mess12:36
piggz[m]Ok, im onboard with that12:56
piggz[m]will you just copy the meta config from piggz repo?12:56
riniguspiggz: I will look into it tonight. let's start by making chum:toolkit project and add sb2 there for chum and chum:testing. will use your repo config for chum:toolkit arch64_5.1 only - for a start and add it to :testing arch64_5.1.13:44
rinigusunless someone objects before that13:44
piggz[m]Ok, sounds good.  I am going MTB for a few hours tonight, so expect it will be done by the time i get back :D13:51
riniguspiggz: looks like you have sb2 together with qt6 packages. I'd prefer to keep them separate. will run smaller test first to figure out how it works17:06
riniguspiggz: tried to model it similar to sailfish:5.1, see https://build.sailfishos.org/project/show/home:rinigus:sb2 . and testing it against https://build.sailfishos.org/project/show/home:rinigus:tmp18:10
riniguswhat I cannot figure out is how do I know which sb2 was used18:10
rinigusany tips?18:10
malis there list of packages it installs in build logs18:14
mallike this [    4s] [28/175] cumulate libsb2-2.3.90+git58+syscall_forwarding_refactored_jb59837_pgz.20251005175244.582f760-1.1.1.bso18:15
riniguslet me check18:17
rinigusmal: which package do you see this libsb2? all I can see is "[5/217] cumulate sb2-tools-aarch64-dependency-inject-1.0+git34-1.4.1.bso"18:19
rinigusfor example in https://build.sailfishos.org/build/home:piggz:qt6sb2/sailfish_51_aarch64/aarch64/qt6-qtbase/_log18:21
rinigusfound it - in sb2-tools-aarch6418:23
malyes, and you can compare the build number of that sb2-tools-aarch64-dependency-inject-1.0+git34-1.4.1.bso with the builds to see from which one it took it18:23
rinigusthanks. looks like I need to boost the end counter - mine was 1.1.118:28

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!