| *** ChanServ sets mode: +v T4 | 05:29 | |
| *** svalx_ is now known as svalx | 07:13 | |
| *** svalx_ is now known as svalx | 07:18 | |
| *** svalx_1 is now known as svalx | 08:07 | |
| T4 | Migoas was added by: Migoas | 08:36 |
|---|---|---|
| T4 | <akaWolf> "In first we must update mic in sdk" … https://wiki.merproject.org/wiki/Nemo/Glacier#Build_image_youself … what is for? | 09:55 |
| T4 | <akaWolf> ```$ mic --version … [09/29 09:54:21] : mic 0.14 (Sailfish OS 2.2.1.18 (Nurmonjoki))``` | 09:55 |
| *** ChanServ sets mode: +o faenil_ | 10:53 | |
| *** olesalscheider_ is now known as olesalscheider | 10:56 | |
| T4 | <neochapay> @akaWolf ["In first we must update mic in sdk" … https://w …], It was for old version I think... | 12:46 |
| T4 | <meierrom> @akaWolf ["In first we must update mic in sdk" … https://w …], https://wiki.merproject.org/wiki/Image_Creation_For_Beginners | 13:37 |
| Leif_Erikson | Hello, I'm still trying to build the Glacier home project and struggling with the build error "Project ERROR: nemodevicelock development package not found" | 13:37 |
| Leif_Erikson | How can I solve this issue? I remember, that I have to add another repo to the build engine. What is the correct command to do that? | 13:38 |
| mal | so you are using platform sdk or something else? | 13:38 |
| Leif_Erikson | Yes, the documentation says, that the platform sdk is installed on the build engine of the app sdk. | 13:39 |
| T4 | <akaWolf> ? | 13:39 |
| Leif_Erikson | I trigger the build from Qt Creator of the app sdk. | 13:39 |
| mal | I have no idea what you mean by that you installed it on the build engine of app sdk | 13:40 |
| T4 | <akaWolf> Yeah | 13:40 |
| r0kk3rz | mal: build engine == build vm | 13:40 |
| T4 | <akaWolf> Right, App SDK conrains 2 vm | 13:41 |
| mal | r0kk3rz: I still don't understand what he means | 13:42 |
| r0kk3rz | Leif_Erikson: surely you've learnt how to ssh into the build vm by now | 13:42 |
| T4 | <akaWolf> I wouldnt use vm. There is ready docker images... | 13:43 |
| T4 | <akaWolf> mal, me too :) | 13:44 |
| r0kk3rz | @akaWolf, im pretty sure hes developing on windows... | 13:44 |
| r0kk3rz | so yeah, vms | 13:44 |
| T4 | <akaWolf> Oh | 13:44 |
| Leif_Erikson | Yes, I can connect to the build vm. I have already installed the lipstick-qt5-devel package as suggested in this channel. | 13:45 |
| T4 | <akaWolf> mb2 is working on top of sb2, right? | 13:45 |
| r0kk3rz | generally you shouldnt have to install packages manually like that | 13:45 |
| Leif_Erikson | I'm developing on macOS | 13:45 |
| r0kk3rz | only add extra repos | 13:45 |
| T4 | <akaWolf> sb2 is a wrapper for chroot? | 13:46 |
| mal | you really rarely need to install anything manually if you have correctly set dependencies in spec file | 13:46 |
| T4 | <akaWolf> mb2 read spec and run sb2, iiuc... | 13:47 |
| Leif_Erikson | Sunds plausible to add a repository. I know this approach from Maven for Java projects. I have checked out the development branch of Glacier home and expected, that the spec file includes everything I need. | 13:48 |
| Leif_Erikson | Maybe I have to add the missing repositories on the build vm. | 13:48 |
| mal | it does | 13:48 |
| mal | so the missing repo is the most likely issue | 13:49 |
| T4 | <akaWolf> I also will build glacier home | 13:49 |
| T4 | <akaWolf> mal, what about sb2 and mb2? | 13:49 |
| Leif_Erikson | I assume, the Nemo Mobile repo is missing. There is just the Sailfish repos pre-installed. | 13:49 |
| mal | Leif_Erikson: I think that is not the problem, app sdk is setup to build apps, not whole UI code | 13:50 |
| Leif_Erikson | How can I add the Nemo Mobile? I mean: Which command do I have to use, after I have logged into the build vm? | 13:51 |
| mal | show what repos you have enabled in the build engine now | 13:52 |
| r0kk3rz | and show your .spec | 13:52 |
| T4 | <akaWolf> hey, guys, what is mb2 and sb2?) | 13:53 |
| mal | r0kk3rz: he tries to build glacier-home using app sdk, not using platform sdk which is the one that should be used | 13:53 |
| r0kk3rz | mal: i know | 13:53 |
| mal | r0kk3rz: do you have knowledge about the internals of build engine, I mean does it use sb2 internally there or how the repos are setup | 13:53 |
| r0kk3rz | afaik it basically is the platform sdk in a vm | 13:53 |
| mal | but with different repos enabled it seems | 13:54 |
| r0kk3rz | it definitely uses sb2 | 13:54 |
| Leif_Erikson | https://pastebin.com/2YNDJcYi | 13:54 |
| T4 | <akaWolf> @r0kk3rz [afaik it basically is the platform sdk in a vm], it based at platform sdk | 13:54 |
| r0kk3rz | maybe different repos | 13:54 |
| T4 | <akaWolf> build engine - platform sdk + targets | 13:54 |
| mal | Leif_Erikson: ssu lr | 13:54 |
| mal | or more like using sb2 | 13:55 |
| mal | wondering what the target name is in app sdk | 13:55 |
| r0kk3rz | @akaWolf what on earth are you going on about? | 13:55 |
| akaWolf | about platform sdk :) | 13:56 |
| akaWolf | but nvm | 13:56 |
| r0kk3rz | Leif_Erikson: from my sdk the right packages should be available in the default repos | 13:56 |
| akaWolf | how sb2 is working? | 13:56 |
| r0kk3rz | so im guessing the .spec doesnt have the right bits | 13:56 |
| akaWolf | is it chrooting or what? | 13:56 |
| mal | Leif_Erikson: for some reason you have been spending days and days on debugging an issue because you are trying to do thing in non-default way | 13:56 |
| r0kk3rz | akaWolf: its a cross compiler, it uses qemu | 13:57 |
| Leif_Erikson | https://pastebin.com/TyWS0TXM | 13:57 |
| akaWolf | r0kk3rz: interesting, what about mb2? | 13:57 |
| r0kk3rz | same thing | 13:57 |
| akaWolf | but IIUC it's on top of sb2 | 13:57 |
| mal | akaWolf: you are overthinking the whole thing | 13:58 |
| akaWolf | mal: xD | 13:58 |
| r0kk3rz | yeah it is, its all about making rpm packages | 13:58 |
| akaWolf | yeah | 13:58 |
| akaWolf | mb2 -t SailfishOS-armv7hl -s rpm/sailfish-browser.spec build | 13:58 |
| akaWolf | like so | 13:58 |
| r0kk3rz | yes i have used it before :) | 13:58 |
| akaWolf | looks like it also possible to build packages locally using osc | 13:59 |
| akaWolf | what is for? | 13:59 |
| r0kk3rz | osc is using OBS | 13:59 |
| Leif_Erikson | I have read in the documentation of Jolla, that the platform sdk is installed on the build vm. Anyway: If not I can use another approach to build and deploy Glacier home. I have also installed both the app and platform sdk on aLinux vm on my Mac. Unfortunately it is not possible to install the platform sdk directly on macOS. | 14:01 |
| akaWolf | https://wiki.merproject.org/wiki/Building_against_Mer_in_Community_OBS#local_build | 14:01 |
| akaWolf | r0kk3rz: ^ | 14:01 |
| akaWolf | there is local build! | 14:01 |
| r0kk3rz | yes | 14:01 |
| r0kk3rz | but it still uses OBS | 14:01 |
| akaWolf | hm how :) | 14:02 |
| akaWolf | if it local.. | 14:02 |
| r0kk3rz | because it downloads stuff off the OBS to run locally | 14:02 |
| mal | r0kk3rz: btw, I have never tried to ssh into the build engine, where can I find the ip and port | 14:04 |
| Leif_Erikson | ssh -p 2222 -i ~/SailfishOS/vmshare/ssh/private_keys/engine/mersdk mersdk@localhost | 14:04 |
| akaWolf | mal: vm settings | 14:05 |
| akaWolf | port routing | 14:06 |
| r0kk3rz | mal: https://sailfishos.org/wiki/Tutorial_-_Building_packages_manually | 14:06 |
| akaWolf | no need to use VM et all | 14:07 |
| akaWolf | build engine is the same platform sdk | 14:07 |
| mal | found it | 14:07 |
| r0kk3rz | Leif_Erikson: anyway, show your spec | 14:08 |
| Leif_Erikson | I think it os the last version of the development branch: https://pastebin.com/JdB3gWrE | 14:09 |
| akaWolf | r0kk3rz, Requires is at run stage only? | 14:12 |
| r0kk3rz | it is | 14:12 |
| akaWolf | for build only BuildRequires? | 14:12 |
| r0kk3rz | yeah, its all .rpm standard stuff, theres plenty of resources online for all the various syntax | 14:13 |
| akaWolf | btw I would add jolla home to Conflicts | 14:14 |
| akaWolf | Leif_Erikson: where did you found instructions to build glacier home? | 14:16 |
| r0kk3rz | instructions? you just build it | 14:17 |
| akaWolf | well I mean there is no links to build instructions here: https://wiki.merproject.org/wiki/Nemo/Glacier | 14:18 |
| Leif_Erikson | Indeed. It was my assumption, that I can build and deploy the project from Qt Creator. | 14:19 |
| akaWolf | I would build from CLI | 14:19 |
| r0kk3rz | you can do either | 14:21 |
| Leif_Erikson | The link, that was posted some minutes ago, refers to the whole Mer project, doesn't it? I thought that I could build Glacier home locally more easy and quick. If you develop on modification you might want to code and test in short iterations. | 14:21 |
| akaWolf | r0kk3rz: well CLI is more straightforward | 14:21 |
| mal | Leif_Erikson: run something like this in the mersdk via ssh sb2 -t SailfishOS-2.2.1.18-i486 -R -m sdk-install zypper in nemo-qml-plugin-devicelock-devel | 14:21 |
| r0kk3rz | akaWolf: you can do whatever you like | 14:22 |
| akaWolf | r0kk3rz: ofc, but when you have an errors | 14:22 |
| Leif_Erikson | I'll try. | 14:22 |
| akaWolf | I would use more direct path | 14:22 |
| mal | Leif_Erikson: finding which package to install should have been simple, just using sb2 -t SailfishOS-2.2.1.18-i486 -R -m sdk-install zypper se lock | 14:22 |
| r0kk3rz | its in the pkgconf, so it should be pulling it in already | 14:23 |
| mal | Leif_Erikson: of course that is for running in emulator, for device change the target name | 14:23 |
| mal | sdk-assistant list tells available targets | 14:24 |
| mal | r0kk3rz: a bit annoying that app sdk doesn't handle installing dependencies easily | 14:24 |
| r0kk3rz | it does though | 14:25 |
| mal | not in this case | 14:25 |
| r0kk3rz | if its a standard mer thing, sticking in the spec is typically all you need | 14:26 |
| r0kk3rz | Leif_Erikson: what arch are you building for? | 14:26 |
| mal | r0kk3rz: but it complains about dependencies which I can simply install via ssh | 14:27 |
| mal | r0kk3rz: so why didn't it find those | 14:27 |
| r0kk3rz | its a mystery | 14:27 |
| mal | so it knows what it wants but doesn't find those eventhough those are available | 14:28 |
| r0kk3rz | or more likely Leif_Erikson is somehow doing it wrong | 14:28 |
| mal | anyway glacier-home won't package properly in app sdk | 14:28 |
| mal | r0kk3rz: I tried it myself | 14:28 |
| Leif_Erikson | The build was completed successfully. I only see the warning "NOTICE: This specfile does not have the qtc_* macros defined" | 14:29 |
| akaWolf | hm | 14:31 |
| Leif_Erikson | The deployment failed with the error "Error: nothing provides glacier-settings needed by lipstick-glacier-home-qt5-0.27-2.i486 Finished transaction (status=2, runtime=71ms)" | 14:31 |
| Leif_Erikson | I first tried to deploy on the simulator. I will check it with my developer device. | 14:31 |
| akaWolf | you need to build different arch for device | 14:31 |
| akaWolf | mal: looks like nemodevicelock is a wrong package name | 14:32 |
| akaWolf | this explains problem | 14:32 |
| r0kk3rz | no the name is fine | 14:33 |
| akaWolf | why? | 14:33 |
| akaWolf | nemo-qml-plugin-devicelock-devel | 14:33 |
| r0kk3rz | because its a pkgconf name | 14:33 |
| akaWolf | ah ok | 14:33 |
| akaWolf | it's okay if build system can't find package by pkgconf name | 14:34 |
| mal | akaWolf: no it's not, it uses pkgconfig to find the package | 14:34 |
| akaWolf | mal: yeah, but how should sb2 find package name from pkgconf name | 14:35 |
| mal | Leif_Erikson: so either add the nemo ux repo or build it manually | 14:35 |
| akaWolf | it can do that if package already installed | 14:35 |
| mal | akaWolf: pkgconfig like I just said | 14:35 |
| mal | stop overthinking | 14:36 |
| akaWolf | pkgconfig works with installed files! | 14:36 |
| r0kk3rz | Leif_Erikson: yeah ok the .spec needs a few modifications to work with the app sdk | 14:36 |
| mal | akaWolf: that method has been used for finding packages for ages, just trust me, it's correct | 14:36 |
| akaWolf | how can it work? | 14:37 |
| mal | akaWolf: I haven't looked into source code so I don't know, it just works | 14:37 |
| akaWolf | xD | 14:37 |
| akaWolf | not always looks like | 14:37 |
| akaWolf | as we just saw | 14:37 |
| akaWolf | I don't believe in magic :) | 14:38 |
| mal | well that is a completely unrelated issue, some configuarion error or somethign | 14:38 |
| r0kk3rz | it was missing some magic macros | 14:38 |
| r0kk3rz | built fine for me | 14:38 |
| mal | r0kk3rz: ? | 14:38 |
| r0kk3rz | installed all the deps as it should | 14:39 |
| mal | I get an error about not finding rpm/lipstick.service | 14:39 |
| mal | r0kk3rz: hmm | 14:39 |
| mal | r0kk3rz: which macros | 14:39 |
| r0kk3rz | mal: https://gist.github.com/r0kk3rz/8566d1ae16c0a3b984b9dc7140f655d1#file-gistfile1-txt-L1-L4 | 14:40 |
| r0kk3rz | and these ones were different - https://gist.github.com/r0kk3rz/8566d1ae16c0a3b984b9dc7140f655d1#file-gistfile1-txt-L50-L52 | 14:40 |
| mal | hmm, never seen those before | 14:40 |
| Leif_Erikson | How can I add the nemo ux repo. I think, again with the mb2 command? | 14:40 |
| akaWolf | r0kk3rz: if you already have the package, which install pkgconfig rule, which contains «nemodevicelock», it should be fine, but otherwise I don't see any way to know that we need «nemo-qml-plugin-devicelock-devel» without introspecting into all pkgconfig rules into all packages... | 14:40 |
| r0kk3rz | Leif_Erikson: replace the .spec with the one i just posted and build again | 14:41 |
| r0kk3rz | akaWolf: and yet, it works | 14:41 |
| akaWolf | how?? | 14:41 |
| r0kk3rz | magnets | 14:41 |
| akaWolf | .. | 14:41 |
| akaWolf | only if rpm place pkgconfig name into internal package description | 14:42 |
| r0kk3rz | wut? | 14:43 |
| akaWolf | when building rpm | 14:43 |
| Leif_Erikson | First or second link? | 14:43 |
| r0kk3rz | Leif_Erikson: its the same link | 14:43 |
| mal | r0kk3rz: not sure why build fails for me on that lipstick.service file | 14:43 |
| mal | r0kk3rz: not quite sure why those macros are needed and why the normal unwrapped ones don't work | 14:44 |
| akaWolf | r0kk3rz: which error did you solve by modifying so that .spec? | 14:44 |
| r0kk3rz | akaWolf: the one where it wasnt pulling it its dependencies | 14:45 |
| mal | akaWolf: dependencies | 14:45 |
| mal | r0kk3rz: to me those macros seem just like dummy wrappers, or does build override those | 14:45 |
| akaWolf | «nemo-qml-plugin-devicelock-devel»? | 14:45 |
| mal | any dependency | 14:46 |
| Leif_Erikson | I think I have the same problem as mal: https://pastebin.com/DFhbZzC4 | 14:46 |
| r0kk3rz | mal: yes, something else must be happening... there was a warning about missing them before | 14:46 |
| akaWolf | how can qmake call be related to dependencies?! | 14:47 |
| mal | r0kk3rz: did you get the error about service file? | 14:47 |
| mal | akaWolf: nobody knows, and we don't care why, it just seems to work | 14:47 |
| r0kk3rz | mal: i didnt build the whole rpm i admit, but it did install the deps and build the project | 14:47 |
| mal | ok | 14:47 |
| r0kk3rz | afaik you need to have *all* the files listed in the .pro | 14:47 |
| akaWolf | sorry, guys, but I feel: fuck rpm! | 14:47 |
| r0kk3rz | akaWolf: this isnt an rpm thing | 14:48 |
| mal | akaWolf: compared the debian packaging spec is much nicer | 14:48 |
| r0kk3rz | this is an app sdk toolchain thing, which is a bit of a house of cards | 14:48 |
| akaWolf | no, in a good product should be no magic | 14:49 |
| r0kk3rz | hah | 14:49 |
| r0kk3rz | well go and make this magicless project | 14:49 |
| r0kk3rz | because you wont find it here | 14:50 |
| akaWolf | I'm fine with PKGBUILD, for example | 14:50 |
| Leif_Erikson | I learned from the author of the lipstick example project, that the .service file is essential, because a lipstick implementation is a systemd's user session. | 14:50 |
| mal | r0kk3rz: adding the file to pro doesn't seem to help, maybe I'm doing something wrong | 14:50 |
| T4 | <faenil> I think the most productive criticism is the one that is followed by a bugfix :) otherwise it is of no help... | 14:51 |
| akaWolf | where is bugfixing me? :) | 14:51 |
| T4 | <faenil> ...no help here, where there is barely enough manpower to push the whole thing forward | 14:51 |
| r0kk3rz | mal: maybe something is getting confused with the subproject | 14:52 |
| r0kk3rz | @faenil: hows things? | 14:52 |
| T4 | <faenil> Not bad :) yourself? | 14:53 |
| r0kk3rz | yeah pretty good, busy busy | 14:54 |
| T4 | <faenil> Hehe | 14:54 |
| T4 | <faenil> Good, glad to hear. I need to start playing with hw adaptation...have been meaning to do it for a long time | 14:55 |
| akaWolf | should be time for rest... | 14:55 |
| r0kk3rz | @faenil: whatcha going to port to? | 14:55 |
| T4 | <faenil> My next phone :) i.e. don't know yet | 14:56 |
| r0kk3rz | ah | 14:56 |
| akaWolf | iPhone? :) | 14:56 |
| r0kk3rz | you should get all the freebies from your corporate overlords | 14:56 |
| mal | r0kk3rz: yep, somehow this doesn't like to find the rpm folder | 14:57 |
| T4 | <faenil> Sony xz2 compact, or Galaxy S9...or any new compact smartphone coming in the next few months | 14:57 |
| mal | or copy it's contents | 14:57 |
| T4 | <faenil> Freebies? What's that :D | 14:57 |
| r0kk3rz | heh | 14:57 |
| r0kk3rz | i think the compacts are about finished | 14:58 |
| r0kk3rz | these days its all 5.5"+ | 14:58 |
| T4 | <akaWolf> @faenil [Sony xz2 compact, or Galaxy S9...or any new co …], sounds cool | 14:58 |
| T4 | <faenil> Sad, but likely true :( xz2 compact is probably the last high end compact we'll see :( | 14:58 |
| T4 | <akaWolf> I'm complaining that new Jolla's port to XA2 would be even worse then X in case of SoC | 14:59 |
| T4 | <akaWolf> we should have port to the top HW | 15:00 |
| r0kk3rz | why? im sure sailfish will work on the xa2 just fine | 15:00 |
| T4 | <akaWolf> XA2 is even worse then X | 15:01 |
| r0kk3rz | the top hw usually has all kinds of fancy features which sailfish doesnt support | 15:01 |
| T4 | <akaWolf> X was 2 years ago | 15:01 |
| T4 | <akaWolf> look at Pocophone X1 | 15:01 |
| T4 | <akaWolf> for example | 15:01 |
| Leif_Erikson | We are waiting for our Accione P developer devices. The specification looks interesting. | 15:02 |
| Leif_Erikson | If the deployment doesn't work with the app sdk. Does someone know a different approach for the deployment? | 15:03 |
| r0kk3rz | it'll work, it just needs some hacking | 15:05 |
| mal | r0kk3rz: funny thing, when building the glacier-home using mb2 via ssh in mersdk it builds fine so what does sdk do differently | 15:06 |
| Leif_Erikson | I just update my developer device with pkcon refresh, pkcon install lipstick-glacier-home-qt5 and systemctl --user restart lipstick. Are the cool system controls for swipe in at the top of the screen in another branch than the developer branch? Is this the manhatten branch? | 15:08 |
| mal | which branch are you using? | 15:10 |
| mal | the ones built on OBS are from master branch which might not have all things | 15:10 |
| Leif_Erikson | I used the suggested one from the Wiki: ssu ar http://repo.merproject.org/obs/nemo:/devel:/ux/sailfish_latest_armv7hl/ nemo-devel-ux | 15:11 |
| Leif_Erikson | r0kk3rz: I hope someone does this hack. Donation of community members might be a good idea. 100 EUR to make a fix. 50 EUR for a documentation. | 15:13 |
| Leif_Erikson | Something like that | 15:13 |
| Leif_Erikson | The poeple here seem to make a great job to make this project great | 15:14 |
| T4 | <akaWolf> are you working now, Leif_Erikson? | 15:14 |
| T4 | <akaWolf> Leif_Erikson, how did you solve a problem with service? | 15:17 |
| Leif_Erikson | Yes. I time boxed the evaluation for Nemo Mobile on Saturday | 15:17 |
| T4 | <akaWolf> I mean that one: https://pastebin.com/DFhbZzC4 | 15:18 |
| T4 | <akaWolf> nice, I learn Nemo in the free time... | 15:18 |
| T4 | <neochapay> I was say use devel branch | 15:19 |
| Leif_Erikson | I couldn't sole this issue. I learned from r0kk3rz, that it needs some hacking. | 15:19 |
| T4 | <akaWolf> that's deploying issue? | 15:19 |
| Leif_Erikson | YEs, build works for me, deployment not. | 15:21 |
| mal | Leif_Erikson: I still wondering why you feel that simply running two commands in a terminal instead of hours and hours of debugging is too much? | 15:21 |
| Leif_Erikson | I would be glad to know the two commands. | 15:22 |
| mal | as linked earliet today https://sailfishos.org/wiki/Tutorial_-_Building_packages_manually | 15:22 |
| mal | section building packages | 15:22 |
| mal | and then there is next section about deploying and running it | 15:23 |
| T4 | <akaWolf> that's the same | 15:23 |
| T4 | <akaWolf> as Leif_Erikson doing | 15:23 |
| mal | no it's not because that way build works fine | 15:23 |
| mal | not error about service or anything like that | 15:24 |
| T4 | <akaWolf> what is the difference then? | 15:24 |
| mal | *no | 15:24 |
| mal | different way of building | 15:24 |
| mal | I have no idea how sdk does the build | 15:24 |
| T4 | <akaWolf> I'm not sure why you think this is different | 15:25 |
| T4 | <akaWolf> the same VM from App SDK | 15:25 |
| T4 | <akaWolf> the same ssh | 15:25 |
| T4 | <akaWolf> and so on :) | 15:26 |
| r0kk3rz | and yet, different results | 15:27 |
| r0kk3rz | curious | 15:27 |
| T4 | <akaWolf> what is different? | 15:27 |
| T4 | <akaWolf> really | 15:27 |
| r0kk3rz | one works, the other throws an error | 15:27 |
| T4 | <akaWolf> nope, what is difference in building? | 15:27 |
| Leif_Erikson | Surprisingly, the manual build throws an error: https://pastebin.com/yq84Rhz5 | 15:28 |
| Leif_Erikson | From Qt Creator, not. | 15:28 |
| Leif_Erikson | I used this command in the project home: mb2 -t SailfishOS-2.2.1.18-i486 build | 15:29 |
| mal | heh, interesting typo in the filenames | 15:29 |
| Leif_Erikson | Indeed | 15:31 |
| T4 | <akaWolf> Leif_Erikson, what is the difference that way with what you did before? | 15:32 |
| mal | Leif_Erikson: so package the files, add to the files section of spec | 15:32 |
| mal | @akaWolf we already said, mb2 build versus what ever app sdk uses | 15:33 |
| Leif_Erikson | I followed the recommendation to do a manual build. I switched to the project root within the build engine and executed the command. Before I clicked on the build button in Qt Creator of the Sailfish app sdk. | 15:33 |
| T4 | <akaWolf> what uses app sdk? | 15:33 |
| Leif_Erikson | The same build engine I used for the manual build. | 15:35 |
| r0kk3rz | @akaWolf: sorry, you've exhausted your question limit today, try again later | 15:35 |
| T4 | <akaWolf> xD | 15:36 |
| mal | @akaWolf you have been asking the same questions over and over again and we said we don't know | 15:36 |
| T4 | <akaWolf> App SDK is the same in both flow, that's why I'm asking | 15:37 |
| mal | something is different and we have no idea what | 15:37 |
| T4 | <akaWolf> mb2 is also about App SDK, that what I mean | 15:37 |
| T4 | <akaWolf> IIUC, the difference is only with using QtC for building or not using | 15:38 |
| Leif_Erikson | I can try to trigger the build with the platform sdk on my Linux vm, that I've installed as described in Jolla's tutorial. But I don't think, this makes any difference. | 15:38 |
| mal | Leif_Erikson: did you try adding the missing files to spec | 15:39 |
| Leif_Erikson | No, do I have to do this as another "Requires" argument? | 15:42 |
| Leif_Erikson | Requires: glacer-home.ts | 15:43 |
| Leif_Erikson | Like this? | 15:44 |
| mal | NO | 15:44 |
| Leif_Erikson | In the %files section? | 15:44 |
| mal | Leif_Erikson: https://github.com/nemomobile-ux/glacier-home/blob/master/rpm/lipstick-glacier-home-qt5.spec#L68 you add %{_datadir}/lipstick-glacier-home-qt5/translations after that linked line | 15:44 |
| r0kk3rz | Leif_Erikson: yeah mate, you've completely missed what that requires stuff is all about | 15:44 |
| Leif_Erikson | This are the libraries, right? | 15:45 |
| T4 | <akaWolf> that's about packagin | 15:46 |
| T4 | <akaWolf> g | 15:46 |
| mal | Leif_Erikson: you now confusing things completely, those are just some files the build produces and all generated files need to be packaged | 15:46 |
| Leif_Erikson | Like StoreKit.framework and webkit.framework in the macOS world. | 15:46 |
| T4 | <akaWolf> btw I just build successfully | 15:47 |
| T4 | <akaWolf> latest devel branc | 15:47 |
| T4 | <akaWolf> h | 15:47 |
| Leif_Erikson | Congratulation | 15:47 |
| T4 | <akaWolf> mal, your experiment was with QtC? when you got the same error as Leif_Erikson | 15:48 |
| Leif_Erikson | I use the updated .spec file, that was posted about an hour ago. | 15:48 |
| T4 | <akaWolf> I didnt | 15:48 |
| mal | akaWolf: which error | 15:48 |
| T4 | <akaWolf> just latest devel | 15:48 |
| T4 | <akaWolf> mal, let me find... | 15:48 |
| mal | and which method did you use for build | 15:48 |
| Leif_Erikson | Ok. I exchange the spec file again and try it again | 15:49 |
| akaWolf | 17:28:36 mal anyway glacier-home won't package properly in app sdk | 15:49 |
| akaWolf | 17:28:43 mal r0kk3rz: I tried it myself | 15:49 |
| r0kk3rz | wtf you actually did a thing? | 15:49 |
| akaWolf | ? | 15:49 |
| mal | akaWolf: that was when using app sdk for build | 15:49 |
| mal | akaWolf: and still is | 15:50 |
| akaWolf | mal: I also used app sdk | 15:50 |
| Leif_Erikson | Indeed, the manual build works now with the original spec file. | 15:50 |
| akaWolf | yeah | 15:50 |
| akaWolf | git checkout; cd; mb2 -t SailfishOS-2.2.1.18-i486 build | 15:51 |
| akaWolf | from the first attempt | 15:51 |
| mal | akaWolf: you mean you built it successfully by pressing the green arrow button in the app sdk UI? | 15:51 |
| akaWolf | mal: nope, sb2 | 15:51 |
| akaWolf | mb2* | 15:51 |
| mal | akaWolf: then you are again confusing things | 15:51 |
| mal | akaWolf: app sdk in this case means UI based build | 15:51 |
| akaWolf | okay, I see, so the error only from QtC | 15:51 |
| akaWolf | yeah, that's our misunderstanding | 15:52 |
| akaWolf | becouse App SDK is two VMs, QtC and docs | 15:52 |
| akaWolf | a* | 15:52 |
| mal | I didn't understand what you meant by qtc until now | 15:52 |
| akaWolf | yeah | 15:52 |
| akaWolf | I suggested to use manual way few hours ago :) | 15:53 |
| Leif_Erikson | Both seem to work: mb2 build and pressing the build button in Qt Creator. | 15:54 |
| Leif_Erikson | Now the challenge is the deployment. | 15:54 |
| akaWolf | hm, what changed? | 15:54 |
| mal | akaWolf: well I suggested it days or weeks ago | 15:54 |
| akaWolf | haha, ok, I didnt see | 15:54 |
| Leif_Erikson | I will try this: mb2 --device "SailfishOS Emulator" deploy --sdk | 15:54 |
| mal | akaWolf: I suggested using platform sdk | 15:54 |
| akaWolf | it's pretty the same thing | 15:54 |
| mal | akaWolf: directly that is, it's used of course in vm also | 15:55 |
| Leif_Erikson | But I think there is another command necessary to restart lipstick, isn't it? | 15:55 |
| mal | Leif_Erikson: how did you fix the build when using build button? | 15:55 |
| akaWolf | yeah, that's interesting | 15:55 |
| akaWolf | Leif_Erikson: you need to restart home screen, I think | 15:56 |
| mal | Leif_Erikson: did you start using devel branch? because that has fixes for build | 15:56 |
| akaWolf | bottomline: never use big green buttoms :) | 15:57 |
| akaWolf | n* | 15:57 |
| mal | only red buttons that say "do not press"? | 15:58 |
| akaWolf | yeah, but never -- green one "make good" | 15:58 |
| Leif_Erikson | Yes, it's the devel branch. I will re-check it with a terminal command. I've used the macOS app "Tower" for check out. | 16:00 |
| akaWolf | use CLI :) | 16:00 |
| Leif_Erikson | Strange error message after triggering the deployment: | 16:00 |
| Leif_Erikson | Fatal: No spec file found in './rpm/' and couldn't make one from a yaml #1 | 16:00 |
| -Github[m]- https://github.com/nemomobile-ux/glacier-home/pull/1 : Proper closing button and black toolbar. | 16:00 | |
| Leif_Erikson | There is a spec file in this directory | 16:01 |
| akaWolf | pwd | 16:01 |
| akaWolf | hope you are trying «mb2 --device "SailfishOS Emulator" deploy --sdk» | 16:02 |
| Leif_Erikson | I used mb2 --device "Sailfish OS Emulator" deploy --sdk with just a different naming | 16:05 |
| akaWolf | pwd | 16:05 |
| akaWolf | copy output here | 16:06 |
| Leif_Erikson | In the directory ./rpm/ relative to RPMS I can find lipstick-glacier-home-qt5.spec | 16:07 |
| Leif_Erikson | It's only one line: | 16:08 |
| Leif_Erikson | Fatal: No spec file found in './rpm/' and couldn't make one from a yaml #1 | 16:08 |
| akaWolf | just place terminal output to paste service :) | 16:08 |
| -Github[m]- https://github.com/nemomobile-ux/glacier-home/pull/1 : Proper closing button and black toolbar. | 16:08 | |
| akaWolf | https://paste.akawolf.org/ | 16:08 |
| mal | Leif_Erikson: are you in correct folder | 16:09 |
| akaWolf | yeah that what I tried to learn | 16:09 |
| Leif_Erikson | In RPMS | 16:10 |
| akaWolf | NO | 16:10 |
| akaWolf | you should be in the root of the repository | 16:10 |
| Leif_Erikson | you mean the project? | 16:10 |
| akaWolf | yep | 16:10 |
| akaWolf | cd .. | 16:10 |
| akaWolf | I mean | 16:11 |
| Leif_Erikson | Ok, that's working | 16:11 |
| Leif_Erikson | Now I get the same problem I had before, when I pushed the green button: | 16:12 |
| Leif_Erikson | https://pastebin.com/X9C7LqPb | 16:13 |
| Leif_Erikson | The important message is this, I think: | 16:14 |
| Leif_Erikson | Error: nothing provides glacier-settings needed by lipstick-glacier-home-qt5-0.27-2.i486 | 16:14 |
| Leif_Erikson | we had this discussion before | 16:14 |
| Leif_Erikson | I did exchange the spec file, that was suggested above and run in another orror. | 16:15 |
| akaWolf | you need some repo I think... | 16:16 |
| Leif_Erikson | This is the build error, if I use the alternative spec file from the today's posting: | 16:19 |
| Leif_Erikson | cp: cannot stat `/home/mersdk/share/SailfishOS/projects/build-glacier-home-SailfishOS_2_2_1_18_i486_in_Sailfish_OS_Build_Engine-Debug/rpm/lipstick.service': No such file or directory | 16:19 |
| Leif_Erikson | And from manual build: | 16:21 |
| Leif_Erikson | Installed (but unpackaged) file(s) found: | 16:21 |
| Leif_Erikson | /usr/share/lipstick-glacier-home-qt5/translations/glacer-home_ru.ts | 16:22 |
| Leif_Erikson | Sorry, these are two lines | 16:22 |
| akaWolf | I think no need to modify spec file... | 16:24 |
| akaWolf | try to manual deploy rpm.. | 16:24 |
| Leif_Erikson | YEs, I will try the suggestion with %directory. I have to search the post in this thread. My IRC app is not the most convenience. | 16:26 |
| Leif_Erikson | With manual you mean the mb2 command form above? I think, before I can do this, the build has to be successful. | 16:28 |
| akaWolf | no, I mean you should stop at non-modified spec from devel | 16:29 |
| akaWolf | and after that try to copy rpm to device | 16:29 |
| akaWolf | and zypper in .rpm | 16:29 |
| Leif_Erikson | Ok, I will try this on the emulator and the developer device. | 16:30 |
| Leif_Erikson | In which directory should I copy the rpm file? | 16:31 |
| akaWolf | doesnt matter | 16:31 |
| Leif_Erikson | Ok, thanks. | 16:31 |
| Leif_Erikson | I'll go home now and try It later. I will tell you, whether this approach succeeds. | 16:32 |
| akaWolf | okay | 16:34 |
| *** ChanServ sets mode: +v T4 | 17:50 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!