Dekko2 Developer Community Thread

hummlbach

@doniks ah sorry I meant setup-click-env not setup-dev-env... So what i wanted to suggest was removing the lxd/lxc stuff from setup-click-env and call the script inside docker container(s) by using clickable instead... It could be used to build dekko for armhf in the first step and place and later perhaps also for x86 (not sure and not a must of course but perhaps to have it consistent...).
I haven't it forked yet... If you give me (and others) access to your repo we can work on it together there. Otherwise I would also fork it...

doniks

@hummlbach said in Dekko2 Community Thread:

@doniks ah sorry I meant setup-click-env not setup-dev-env... So what i wanted to suggest was removing the lxd/lxc stuff from setup-click-env and call the script inside docker container(s) by using clickable instead... It could be used to build dekko for armhf in the first step and place and later perhaps also for x86 (not sure and not a must of course but perhaps to have it consistent...).

sounds good. setup-click-env should be for clickable imho and thus lxc should go and be adjusted for the new docker setup. setup-dev-env can be revisited later

I haven't it forked yet... If you give me (and others) access to your repo we can work on it together there. Otherwise I would also fork it...

ok. gitlab is down right now for an hour or so. please request access there when it's back (they have a button to request access)

doniks

Created a branch using your build script:

https://gitlab.com/doniks/dekko/tree/building

Dekko should build, install and run now!

thrrgilag

@doniks said in Dekko2 Developer Community Thread:

Created a branch using your build script:

https://gitlab.com/doniks/dekko/tree/building

Dekko should build, install and run now!

I took it for a spin on my laptop running 18.04 but it failed. (Issue #104 I'm presuming). I tried it on another machine I have with 16.04 still and it was able to build and install. Now onto the next step and try to get things functional.

doniks

@thrrgilag said in Dekko2 Developer Community Thread:

I took it for a spin on my laptop running 18.04 but it failed. (Issue #104 I'm presuming).

Ah, sorry, I guess I wasn't clear enough. Follow the README file in that branch. It will build using the clickable docker container. A different approach than in #104.

I tried it on another machine I have with 16.04 still and it was able to build and install. Now onto the next step and try to get things functional.

Nice!

doniks

@doniks said in Dekko2 Developer Community Thread:

Follow the README file
It will build using the clickable

merged to master now. Let me know how it goes!

thrrgilag

@doniks said in Dekko2 Developer Community Thread:

merged to master now. Let me know how it goes!

Builds fine on my 16.04 machine, but not my 18.04 machine. I'm going to assume I have something sideways there that'll need to be sorted out at some point. But it builds!

Now to figure out why the account setup / settings don't work. I'm assuming that's the same point others are at as well?

doniks

@thrrgilag said in Dekko2 Developer Community Thread:

@doniks said in Dekko2 Developer Community Thread:

merged to master now. Let me know how it goes!

Builds fine on my 16.04 machine, but not my 18.04 machine. I'm going to assume I have something sideways there that'll need to be sorted out at some point. But it builds!

strange. I only have an 18.04 machine to test and it works there. also, since it's clickable (ie, docker) it should be mostly independent from what you have locally ....

Now to figure out why the account setup / settings don't work. I'm assuming that's the same point others are at as well?

That's what I was staring at until my eyes crossed from the plugin stuff

thrrgilag

@doniks said in Dekko2 Developer Community Thread:

strange. I only have an 18.04 machine to test and it works there. also, since it's clickable (ie, docker) it should be mostly independent from what you have locally ....

I clearly got something knackered somewhere.

dekko/upstream/ubuntu-plugin/plugins/core/core.qbs:52:9 Dependency 'Qt.core' not found for product 'Contacts'.
Please create a Qt profile using the qbs-setup-qt tool if you haven't already done so.

That pretty much repeats for the other components until it bombs out.

Luksus

I also tried to build it and got the same error on manjaro.

hummlbach

hey @thrrgilag @Luksus @rudi please try to install qemu-user-static on the host (outside docker)... (sudo apt-get install qemu-user-static)

thrrgilag

@hummlbach that was it! Thanks!

hummlbach

short status:

currently my builds are crashing - no clue yet why. Are your builds still working? (also after updating the docker image, keep the old one... ;))
the branch set_windows_visible fixes the windows/components not showing up problem
atm you need to do sudo apt-get install python3-markdown python3-pip python3-jinja2 python3-html2text; sudo pip3 install pynliner to be able to use the composer -> needs to be shipped with the click
setting up an account works well
writing mail works
reading mail mostly fails: html mails fail to display in my case, on some mails it crashes, text mails work (sometimes)
deleting mails doesn't work, something seems to go wrong with the indexing

I suggest to track these issues at https://gitlab.com/doniks/dekko/.

doniks

@hummlbach said in Dekko2 Developer Community Thread:

short status:

Thanks for the update! In the weekend I hope to have some time to check it.

I suggest to track these issues at https://gitlab.com/doniks/dekko/.

As for issue tracking ... my thinking is, I want to minimize the disconnect to Dan's upstream. Having a forked git repo is no biggie. We can ensure to remain mergeable. However, setting up a separate infrastructure to track issues would increase the divide. Maybe we can keep low-overhead quick and dirty issue lists in here, similar to your last post. But if we want to track for a longer time and collect reproductions, patches, whatnot, then I prefer to use Dan's tracker. What do you think? Maybe there is some tagging mechanism....

hummlbach

As discussed on telegram we use dekkoprojects issue tracker at https://gitlab.com/dekkoproject/dekko/issues/ to coordinate our efforts and have issues to refer to in commits...

thrrgilag

@hummlbach said in Dekko2 Developer Community Thread:

short status:

currently my builds are crashing - no clue yet why. Are your builds still working? (also after updating the docker image, keep the old one... ;))

I'm probably missing something obvious but my builds keep crashing, is it something to do with the docker image for building the package?

My docker skills are non-existent so I guess it's time I finally educate myself.

doniks

@thrrgilag logfile?

thrrgilag

@doniks that's the annoying part a log doesn't get created, it fails as soon as it starts it seems.

I did load the 0.1.6-alpha0 click you tagged and that worked so I presume something is wrong still with my build environment. Tried blowing away the .build-armhf/ and rebuilding but I don't see anything obvious there. Guess I'll keep digging.

With the 0.1.6-alpha0 click, I was able to confirm that it does render plain text emails but not html ones. Guessing this is related to the existing browser issue where it crashes on certain sites maybe? And I do have one particular email that causes it to segfault outright. Don't know offhand what it in the messages is triggering that though. I was able to send an email though and notifications work so that's something.

hummlbach

@thrrgilag my builds also still crashing... As I said, I think they do since I updated the docker container. I've taken a click that I've built with the old container and "patched" it to the current state. I didn't have time yet to investigate whats the problem with the build currently.
Concerning the mails not getting displayed. Me too thought it was an issue with oxide, but I'm not so sure anymore. The oxide error log messages also appear in 15.04, where all mails are displayed fine. Also I have found some html mails that are displayed fine and some that show up at least partly. But theres a message of the second part of the mail needed to be loaded on opening "failing mails". So perhaps it depends on the size of the mails...(?)

doniks

@thrrgilag said in Dekko2 Developer Community Thread:

@doniks that's the annoying part a log doesn't get created, it fails as soon as it starts it seems.

maybe something in unity8.log then?

another thought: I remember sometime it seemed that UT was cleaning up the log file after the app closed so I had to hack something like this, so I could keep it: while true ; do cat logfile > logfile.keep ; done.