Monday, 2021-12-27

mohjive@piggz: I have problem with errors in qt creator for latest sailfish when opening amazfish project - any ideas?09:45
mohjivethere are two main errors: "please specify platform using FLAVOR=platform" and "Unexpected token"/"Invalid regular expression flag"09:46
piggz[m]mohjive: for building amazfish in sdk, you need to ssh into the build engine and add thechum repository for the dependencies to the build target11:38
mohjiveah, ty, any docu/howto on that?11:40
Thaodanpiggz you can use sfdk11:43
piggz[m]Thaodan: i wondered if that was possible but never figured how11:44
Thaodanpiggz mohjive read here: ther11:45
Thaodan I use chum for build dependencies too and suggest to add them like that ^11:46
piggz[m]mohjive: so, following them instructions, you should add eg to your build target and that should be about all you need11:48
piggz[m](edit if building for 64bit)11:48
rinigusin my experience, from tbuilder days, sfdk is a bit slower than logging into SDK and running `mb2`. but that difference could be rather small for a single project to get annoyed by it11:57
piggz[m]rinigus: i think id better get accepting some PRs!16:29
riniguspiggz: please do, list is getting longer :)16:32
riniguspiggz: if it passes review ..16:33
riniguspiggz: see how it is easier for you to review. ideally, I would have just closed earlier PRs and merge just the last one. then no rebasing is needed and force pushes either. but it is heavier to review...16:51
rinigusif it is too much, then I better start rebasing for the next ones to simplify the reading16:52
piggz[m]rinigus: which s next?16:54
riniguspiggz: 29->31->32 . 32 actually has all changes in, but it is bg :(16:54
piggz[m]rinigus: 29 is approved, some some commented code to remove16:55
riniguspiggz: yes, saw it. I will see what you think of others and maybe can sneak full changeset in 32 . for that code- opened an issue16:56
piggz[m]rinigus: could you merge and rebase 31 pls16:56
riniguspiggz: yes, will merge. sure16:56
riniguspiggz: 31 rebased16:58
mohjiveThaodan: ty for the links, will try to follow them, but they do lack some info it seems :)17:09
mohjivethey mention ssh keys, but not how I locate the private key I need to ssh into the env17:09
Thaodanmohjive: PRs welcome :D17:10
mohjiveand sfdk is not added to PATH, so not accessible by default17:10
mohjiveThaodan: what's the repo?17:10
mohjiveand how do I find/sync the ssh keys?17:11
Thaodanthe keys are in the sdk folder in vmshare/ssh17:13
mohjivebtw I used the mingw64 installed with git bash instead of msys (I did use that in an old installation) and it seems to work :)17:14
piggz[m]rinigus: for the SSU PR ... im wondering if we could have an advanced option to specify the repo URL manually ... for, eg my case where im using a cbeta release, and have to specify the last release ... or ... we could add a _latest_ chum release, to make an always available current version available?17:40
riniguspiggz: the both solutions are possible. in cbeta, do you have release as "latest" ? if so, maybe it makes sense to just add latest to chum repos (regular and testing)17:43
piggz[m]rinigus: no, release is a normal release number, so, a chum user in that situation would either have to manually specify either the last chum release, or, if we add it, the _latest release17:44
riniguspiggz: I have to take a break for an hour or so, let's think about it. we can add manual repo specification to gui then, I think.17:46
piggz[m]rinigus: sure, do you want that in this PR or a seperate17:46
riniguspiggz: separate, please. let's open issue regarding it and I will try to fix it asap17:47
rinigusor you could look into it :)17:47
piggz[m]k :)17:47
piggz[m]rinigus: does the gui fail for you when run from qt creator?18:15
riniguspiggz: never did that. but I am not sure it will have permissions for dealing with packages in that case. so, to test, I now start from lipstick as a regular user and follow the logs via journalctl18:31
rinigusso, cannot not run it via ssh login anymore18:32
piggz[m]rinigus: yeah, that seems to be the case18:32
riniguspiggz: well, at least it works for regular users18:32
piggz[m]rinigus: wondering why you chose to do the SSU dbus in C++ and not QML ?18:38
riniguspiggz: since I needed output in Chum C++ class. so, it was simplish to do it there. also parsing dbus output for `ssu lr` analog was a bit involved18:40
rinigusnot sure I could have done it in qml18:40
piggz[m]rinigus: if you want to keep set_status as a macro, then happy to merge ssu19:35
riniguspiggz: I guess I am used to those macros... will merge and rebase the next one19:43
riniguspiggz: pr 32 rebased19:45
riniguspiggz: will add setStatus as a method - missed your latest comment; will push it into packages branch19:54
riniguspiggz: setStatus commit pushed to PR 3220:15
piggz[m]rinigus: whats the {<cog>} icon?20:18
piggz[m]it looks a little mis-aligned20:18
riniguspiggz: forks. haven't had anything better20:19
riniguspiggz: re alignment - right now it is vertical center of it all. not sure it is the best, but alignment by text baseline is trickier there20:20
piggz[m]rinigus: for pure-maps, shouldnt it show 33 and not 0 ?20:20
riniguspiggz: strange, shows 32 over here20:21
rinigusnot zero20:21
piggz[m]hmm, showing 0 for me20:22
riniguspiggz: and the rest works as it should? i.e you can browse issues, see releases?20:24
piggz[m]rinigus: ah, no ... the links are there in the pulley, but not under the screenshots20:25
riniguspiggz: then you switched to regular chum probably.20:25
piggz[m]no, its testing20:26
piggz[m]rinigus: token for unset20:27
rinigusfor me, after update, we have chum repos removed via post script. no idea how to distinguish update from removal in this context. but if it is not the case, I wonder why then20:27
riniguspiggz: grab tokens from OBS20:28
piggz[m]its in my build dir already20:30
riniguspiggz: I'll be off for tonight, thank you for working on it!20:35
piggz[m]rinigus: what folder do the tokens  go in?20:39
riniguspiggz: into the build folder. the one where you run mb2 ... build21:35
piggz[m]rinigus: im doing it from sdk ... and it seems to have trouble finding it21:39
piggz[m]tried build and src folders and ~21:40
piggz[m]rinigus: so, it finds the files in the build dir, and sets them on the cmake command line, but the build command line still has "unset" ...21:50
piggz[m]will force them into the cache21:50
riniguspiggz: we just cannot add them to the source,  github is scanning all commits for tokens and will invalidate it as soon as it is found21:51
rinigusBut other than that, feel free to change its location. I haven't tested if it works at obs21:52
piggz[m]rinigus: i got it to work by updating my cmakecache21:53
piggz[m]rinigus: ok, app works better now :)21:54
riniguspiggz: it should! It's late here, gn!21:56
piggz[m]rinigus: gn21:57

Generated by 2.17.1 by Marius Gedminas - find it at!