| mohjive | @piggz: I have problem with errors in qt creator for latest sailfish when opening amazfish project - any ideas? | 09:45 |
|---|---|---|
| mohjive | there are two main errors: "please specify platform using FLAVOR=platform" and "Unexpected token"/"Invalid regular expression flag" | 09:46 |
| mohjive | :( | 09:49 |
| 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 target | 11:38 |
| mohjive | ah, ty, any docu/howto on that? | 11:40 |
| Thaodan | piggz you can use sfdk | 11:43 |
| piggz[m] | Thaodan: i wondered if that was possible but never figured how | 11:44 |
| Thaodan | piggz mohjive read here: ther | 11:45 |
| Thaodan | here | 11:45 |
| Thaodan | https://docs.sailfishos.org/Tools/Sailfish_SDK/FAQ/#build-engine | 11:45 |
| Thaodan | https://docs.sailfishos.org/Tools/Sailfish_SDK/Deploying_packages/#deploying-from-repository I use chum for build dependencies too and suggest to add them like that ^ | 11:46 |
| Thaodan | https://github.com/communi/communi-sailfish/blob/master/INSTALL.org#python-cairosvg | 11:46 |
| piggz[m] | mohjive: so, following them instructions, you should add eg https://repo.sailfishos.org/obs/sailfishos:/chum/4.3.0.12_armv7hl/sailfishos:chum.repo to your build target and that should be about all you need | 11:48 |
| piggz[m] | (edit if building for 64bit) | 11:48 |
| rinigus | in 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 it | 11:57 |
| piggz[m] | rinigus: i think id better get accepting some PRs! | 16:29 |
| rinigus | piggz: please do, list is getting longer :) | 16:32 |
| rinigus | piggz: if it passes review .. | 16:33 |
| rinigus | piggz: 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 |
| rinigus | if it is too much, then I better start rebasing for the next ones to simplify the reading | 16:52 |
| piggz[m] | rinigus: which s next? | 16:54 |
| rinigus | piggz: 29->31->32 . 32 actually has all changes in, but it is bg :( | 16:54 |
| rinigus | big | 16:54 |
| piggz[m] | rinigus: 29 is approved, some some commented code to remove | 16:55 |
| rinigus | piggz: yes, saw it. I will see what you think of others and maybe can sneak full changeset in 32 . for that code- opened an issue | 16:56 |
| piggz[m] | rinigus: could you merge and rebase 31 pls | 16:56 |
| rinigus | piggz: yes, will merge. sure | 16:56 |
| rinigus | piggz: 31 rebased | 16:58 |
| mohjive | Thaodan: ty for the links, will try to follow them, but they do lack some info it seems :) | 17:09 |
| mohjive | they mention ssh keys, but not how I locate the private key I need to ssh into the env | 17:09 |
| Thaodan | mohjive: PRs welcome :D | 17:10 |
| mohjive | and sfdk is not added to PATH, so not accessible by default | 17:10 |
| mohjive | Thaodan: what's the repo? | 17:10 |
| mohjive | and how do I find/sync the ssh keys? | 17:11 |
| Thaodan | mohjive: https://github.com/sailfishos/docs.sailfishos.org/ | 17:11 |
| Thaodan | the keys are in the sdk folder in vmshare/ssh | 17:13 |
| mohjive | btw 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 |
| rinigus | piggz: 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 release | 17:44 |
| rinigus | piggz: 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 seperate | 17:46 |
| rinigus | piggz: separate, please. let's open issue regarding it and I will try to fix it asap | 17:47 |
| rinigus | or 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 |
| rinigus | piggz: 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 journalctl | 18:31 |
| rinigus | so, cannot not run it via ssh login anymore | 18:32 |
| piggz[m] | rinigus: yeah, that seems to be the case | 18:32 |
| rinigus | piggz: well, at least it works for regular users | 18:32 |
| piggz[m] | rinigus: wondering why you chose to do the SSU dbus in C++ and not QML ? | 18:38 |
| rinigus | piggz: 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 involved | 18:40 |
| rinigus | not sure I could have done it in qml | 18:40 |
| piggz[m] | ok | 18:40 |
| piggz[m] | rinigus: if you want to keep set_status as a macro, then happy to merge ssu | 19:35 |
| rinigus | piggz: I guess I am used to those macros... will merge and rebase the next one | 19:43 |
| rinigus | piggz: pr 32 rebased | 19:45 |
| rinigus | piggz: will add setStatus as a method - missed your latest comment; will push it into packages branch | 19:54 |
| rinigus | piggz: setStatus commit pushed to PR 32 | 20:15 |
| piggz[m] | rinigus: whats the {<cog>} icon? | 20:18 |
| piggz[m] | it looks a little mis-aligned | 20:18 |
| rinigus | piggz: forks. haven't had anything better | 20:19 |
| rinigus | piggz: re alignment - right now it is vertical center of it all. not sure it is the best, but alignment by text baseline is trickier there | 20:20 |
| piggz[m] | rinigus: for pure-maps, shouldnt it show 33 and not 0 ? | 20:20 |
| rinigus | piggz: strange, shows 32 over here | 20:21 |
| rinigus | not zero | 20:21 |
| piggz[m] | hmm, showing 0 for me | 20:22 |
| rinigus | piggz: 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 screenshots | 20:25 |
| rinigus | piggz: then you switched to regular chum probably. | 20:25 |
| piggz[m] | no, its testing | 20:26 |
| piggz[m] | rinigus: token for unset | 20:27 |
| rinigus | for 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 then | 20:27 |
| piggz[m] | s/got | 20:27 |
| rinigus | piggz: grab tokens from OBS | 20:28 |
| piggz[m] | its in my build dir already | 20:30 |
| rinigus | :) | 20:30 |
| rinigus | piggz: 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 |
| rinigus | piggz: into the build folder. the one where you run mb2 ... build | 21:35 |
| piggz[m] | rinigus: im doing it from sdk ... and it seems to have trouble finding it | 21: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 cache | 21:50 |
| rinigus | piggz: we just cannot add them to the source, github is scanning all commits for tokens and will invalidate it as soon as it is found | 21:51 |
| rinigus | But other than that, feel free to change its location. I haven't tested if it works at obs | 21:52 |
| piggz[m] | rinigus: i got it to work by updating my cmakecache | 21:53 |
| rinigus | Nice! | 21:54 |
| piggz[m] | rinigus: ok, app works better now :) | 21:54 |
| rinigus | piggz: it should! It's late here, gn! | 21:56 |
| piggz[m] | rinigus: gn | 21:57 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!