Wednesday, 2021-07-14

T42<adampigg> Ill fix image building soon now obs is up again06:35
T42<shouaccount> I am getting error when building libgbinder, any suggestions?08:03
T42<shouaccount> I think this has something to do with my vm crashing once before I was building08:08
T42<elros34> run git clean -xdf in source directory ad try again08:36
T42<shouaccount> didn't work08:58
T42<Verevka86> comment this line (re @shouaccount: I am getting error w...)09:03
T42<shouaccount> ok tryinh09:03
T42<shouaccount> ok trying (edited)09:03
lbtPSA: some mer/sfos infra will be down as I fix the wiki and update a server09:52
T42<lawless305> There a FAQ as to what all has been ported already etc. etc.12:35
T42<b100dian> This, but it probably doesnt work because of the annoncement above
T42<shouaccount> thanks, it worked although still have to figure out why my build does not boot :0 (re @Verevka86: comment this line ht...)13:40
T42<MyNameIsEarlB> is there a particular log to check if sailfish just shuts down randomly?16:28
T42<MyNameIsEarlB> itll just say goodbye and shut down randomly16:29
T42<Shirley Bell> Forwarded from unknown: 𝚃𝚑𝚊𝚗𝚔 𝚢𝚘𝚞 𝚏𝚘𝚛 𝚋𝚎𝚒𝚗𝚐 𝚜𝚘 𝚐𝚎𝚗𝚎𝚛𝚘𝚞𝚜, 𝚝𝚑𝚘𝚞𝚐𝚑𝚝𝚏𝚞𝚕 𝚊𝚗𝚍 𝚜𝚘 𝚝𝚛𝚞𝚎. 𝚆𝚒𝚝𝚑 $1000 𝚜𝚝𝚊𝚛𝚝-𝚞𝚙 𝚒 𝚖𝚊𝚍𝚎 $7000 𝚃𝚑𝚊𝚗𝚔 𝚢𝚘𝚞 𝚏𝚘𝚛 𝚔𝚎𝚎𝚙𝚒𝚗𝚐 𝚢𝚘𝚞𝚛 𝚠𝚘𝚛𝚍𝚜 𝚊𝚗𝚍 𝚋𝚎𝚒𝚗�17:11
T42<elros34> @MyNameIsEarlB power key press detected by mce should be logged in journalctl. Maybe you have faulty powerkey?17:27
riniguspiggz: had a chance to think about chum repos? I must say that I like that wild west style approach17:32
rinigusand when the wheels will fall off, we can think about lessons learned and what to do better17:32
rinigusat least it will start and will not be wasted for long discussions :)17:33
piggzthere is also the benevolant dicator approach, where only I decide what goes in17:33
rinigusyes, if you wish. it just takes time17:33
rinigus... your time I mean17:34
piggzsure ... some kind of sensible wild west would be good, where we have a quick discussion maybe?17:34
riniguswe can have discussions as well, just not too much :). there is also chum:testing that can be used to see if the package brings whole repo down17:35
rinigusso, we could let all add / change at chum:testing and then few of us promote to :chum17:36
piggzyeah, lets do that17:36
T42<MyNameIsEarlB> Thanks, I'll check out journalctl.17:36
T42<MyNameIsEarlB> It doesn't happen using any other operating system on my Pinephone. I am using an older version though as I can't get the newer one to dl (re @elros34: @MyNameIsEarlB power...)17:36
piggzlbt: first user complaint that they cant install amazifsh on 3.4 (no builds on obs) :P17:36
rinigusas we don't have many SFOS versions supported, it is easy to start with chum as well.17:37
riniguslbt: pretty please - can you add a macro for each supported SFOS version that will indicate the version in corresponding SFOS repo at OBS17:38
piggzrinigus: I suggested that to mal also ... i guess will have to be packages somewhere17:38
riniguspiggz: doesn't have to be. OBS macros can be used for that as well.17:38
lbtwasn't that supposed to happen?17:39
lbtand yes. we can add it to OBS builds17:39
rinigusI opened SFO thread on that a long time ago, no official response yet17:39
rinigusso, OBS is kind of going around it :)17:40
piggzthat would be handy .. for amazfish, mal found a workaround, but its a massive fluke17:40
lbtmal: why don't we define sailfish version in the sdk ? Any idea?17:40
lbtI guess there is the "it's all supposed to be done by features"  argument...17:41
riniguslbt: we would suggest with piggz   to go for a wild west style with chum and, if possible, allow all interested to submit packages to Chum:testing . from :testing, it could be promoted by pinging Chum maintainers.17:43
rinigusas for sfos versioning, still would help with the packaging. for cross-platform apps, it is nice to know if you compile for fedora or sfos, for example17:43
rinigusfedora and suse define those macros, sfos should do too17:44
piggzi agree ... i had case with kcalendarcore being needed for 4.1, but not in prev versions ... so was very hard to write a spec that worked for all versions17:44
lbtI don't want to make chum:testing world writeable as such - people could too easily edit other people's packages17:47
lbthowever allowing anyone to SR packages there is easy - I just make you two admins17:48
lbtand you approve them17:48
lbtyou may want to track who owns which package17:49
lbtwhat macros did you want?17:49
riniguslbt: OK, let's see how it works. no idea what is SR, but I guess it is something like pull request in OBS lingo17:50
piggzlbt: maybe macros like in the abot cross distro howto?17:51
rinigusmacro like `sailfishos_version` and the version encoded. from piggz link, looks like suse is using 1010 for 10.10 version17:51
rinigusso, what would it be for - 40100 should be sufficient?17:52
rinigusas 4.01.00 - 24 is minor anyway17:52
piggzrinigus: maybe 040100 ... to account for sfos 10 :)17:53
lbt4.1.0 should probably be 40100017:53
lbtdo you want to lose the .24 ?17:55
lbtthe other thing we have for every version is like 0.20210714.0.117:56
lbtessentially it's the date of the snapshot17:56
lbtso  that is
piggzooo, leaked version number!17:57
piggzi think we could live without the minor version ... but, if its easy enough to add, there is probably no down side...17:58
piggzi guess we you be writing code such as if sfos_version >= 04010000 ....17:58
lbtyes - lots of trailing zeros is easy to get wrong :/17:59
riniguspiggz: but with sfos 10 it will still be larger than 4. so no need to have front zero. that way version 100 can be handled the same way18:01
rinigusand indeed, too many numbers are easy to get wrong. as for using the date - then we need to consult the table with the dates18:02
lbtso => 4010018:03
rinigusthat is fine by me. piggz ?18:03
rinigusnonono, sorry, that would be -> 4.000118:04
rinigusas in 4.00.0118:04
lbtso => 4010018:05
lbtso 4..0.1.48 => 4000118:05
piggzyeah, i think thats how suse does it after flicking down the list18:05
rinigusjust in case if we have
piggzthey have 9.3 and 10.0, as 930 100018:06
riniguswill be afk for 20-30 mins18:06
piggzlbt: youre on a roll!18:12
piggzlbt: rinigus: maybe a is_sailfishos macro too?18:12
lbtthe existence of sailfishos_version does that18:13
lbt line 3 fyi18:13
T42<elros34> @MyNameIsEarlB then I am not sure it's worth to debug it. Try to download latest version maybe from
piggzlbt: cool, that easy18:15
lbtyes - need to make it part of my import18:15
lbtand of course it won't work in SDKs :(18:15
piggzsure ... have you tried to get 3.4 and 3.3 targets?18:16
piggzso, is community obs on par with internal obs these days?18:17
lbtit's the same codebase18:18
lbtactually I  should be able to copy all the internal _service files for the oss code to community too18:19
lbtit's not that trivial as webhooks works differently internally18:20
lbtI think may be coming to life...18:26
lbtok - try it and let me know...18:27
piggzwill do ...18:30
piggzjust updating volla packages18:30
riniguslbt: thank you very much!18:48
rinigusnow I can start deleting my own sfos detection hacks (as if not suse or fedora, must be sfos)18:49
riniguslbt: we would probably make chum:testing for submissions - this one is missing so far. as for running many chum subrepos separate for each sfos version, this seems to be overkill.18:52
piggzrinigus: except for when packages build against libraries that dont maintain compatibility between versions19:12
piggz:looks at libicu19:13
riniguspiggz: but those could be handled in the same source still - I mean that we don't need this
rinigusinstead, define multiple build targets in the same repo19:13
piggzi thought that was what you were arguing against :)19:14
rinigusat least for the start. there could be packages that don't work with some versions, but it is problem for future19:15
riniguslbt: exactly, that would be easier to maintain. at least at the beginning19:53
lbtand is looking OK20:07
riniguslbt: nice! I'll start on my side tomorrow.20:31
rinigusthank you!20:31
riniguslbt: but those old versions - we don't need aarch64 for those20:32
rinigus3.4.0.24, I mean20:32
lbtOK - I don't have a map of what's needed - it was released so I added it20:47
lbtwant me to remove it ?20:47
piggzlbt: for histric purposes, will you go back to 1.0? :P20:47
lbtpiggz: I might - depends if I automate it ;)20:48
lbtor if people ask for specific versions20:48
lbtI know slava wants some old ones20:48
lbtit's a bit tedious doing it by hand ... so on demand is more likely20:48
lbtat least now we know it will work20:49
piggzlbt: so, shall we assume wednedsays are quiet for you in the future ? ;)20:50
lbtsadly not... I've been swamped at work and finally got some time off - was supposed to be doing stuff outside but ended up doing things that had big "wait gaps" so I made myself useful20:52
lbtplus I got a handle on the issues: we did miss some packages from some releases and we added them to the prjconf to enable rust builds20:53
lbtand now... dinner (late!)20:54
lbtenjoy chum, the macros and the releases - let me know how it's going20:54
mallbt: is there some way to un-break projects without editing service files of each package20:55
malfor older targets20:55
lbtthere's a trigger service20:56
lbtor hit rebuild in the failed build20:57
mallbt: trigger rebuild is not helping20:57
mallbt: for example
malno indication why it thinks it is broken20:58
lbtI think I may need to do a back end prod...21:00
lbtit's going21:02
lbtif you want to prepare a list I need projects / arch pairs that have problems21:02
lbtie this was:   nemo:testing:hw:fairphone:fp2-sibon armv8el21:03
* lbt is afk now o/21:03
mala lot of projects are broken like that21:04

Generated by 2.17.1 by Marius Gedminas - find it at!