• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
UBports Robot Logo UBports Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Updating apps to 16.04

Scheduled Pinned Locked Moved App Development
25 Posts 11 Posters 10.6k Views 5 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D Offline
      DanChapman @zubozrout
      last edited by 23 May 2018, 11:21

      @zubozrout ahh i wonder if click-review was updated in the ubports archive to allow the new framework. Try dropping the framework to a 15.04 one and run click-review to see what the real errors are and then bump it back up before pushing to the store as the framework most likely isn't the issue.

      Support Dekko development: https://www.patreon.com/dekkoproject

      Z 1 Reply Last reply 23 May 2018, 11:43 Reply Quote 0
      • Z Offline
        zubozrout @DanChapman
        last edited by zubozrout 23 May 2018, 11:43

        @danchapman Good idea to test this. It looks like I get the same error for 15.04 (also tested with 15.04.5 which was the framework I originally used for the project).

        1 Reply Last reply Reply Quote 0
        • Z Offline
          zubozrout
          last edited by 23 May 2018, 19:31

          Ok, so there is this ppa https://launchpad.net/~bhdouglass/+archive/ubuntu/clickable with the latest forked package that is even available for bionic :). And it has xenial app support. With that reviewing the packages should work correctly.

          1 Reply Last reply Reply Quote 2
          • D Offline
            doniks
            last edited by 3 Jun 2018, 17:13

            @zubozrout
            I don't get it. I'm looking at the "This app needs to be reviewed manually, please check you app using the click-review command", but I can't figure out how to proceed from here.

            I could run the first two of @DanChapman 's commands (should I have set the PATH_TO_CLICK_DIR variable? to what?).

            H 1 Reply Last reply 3 Jun 2018, 21:15 Reply Quote 0
            • H Offline
              hummlbach @doniks
              last edited by hummlbach 6 Mar 2018, 21:16 3 Jun 2018, 21:15

              @doniks What Dan meant is: go to the directory where the click is. So often the click is in the build subdirectory. In that case you would have to do a cd build and then click-review name-of-your-click.click. Alternatively you may stay in the directory you are and pass the full path to the click over to click-review. Like click-review /home/doniks/my-app/build/my_app.doniks_1.2.3.click or something like that... And then the funny part will start πŸ™‚

              D 1 Reply Last reply 3 Jun 2018, 21:32 Reply Quote 2
              • A Offline
                arubislander
                last edited by arubislander 6 Mar 2018, 21:23 3 Jun 2018, 21:22

                Not to hijack the thread, but I have done this with my click package. It says:

                build/usonic.arubislander_0.6.0_all.click: pass
                

                How do I notify the OpenStore Submit process that the package has passed the click-review?

                πŸ‡¦πŸ‡Ό πŸ‡³πŸ‡± πŸ‡ΊπŸ‡Έ πŸ‡ͺπŸ‡Έ
                Happily running Ubuntu Touch
                Google Pixel 3a (20.04 DEV)
                JingPad (24.04 preview)
                Meizu Pro 5 (16.04 DEV)

                1 Reply Last reply Reply Quote 1
                • D Offline
                  doniks @hummlbach
                  last edited by doniks 6 Mar 2018, 21:43 3 Jun 2018, 21:32

                  @hummlbach Nope, I still don't get it. Inside the container I never see my click, outside the container I never see click-review

                  https://paste.ubuntu.com/p/389kxQ9Nfw/

                  UPDATE: Now, I got it

                  $ docker run -it -v /home/peter/docs/devel/shorter/build/:/clickdir  clickable/ubuntu-sdk:16.04-amd64 bash
                  root@8fe1c0f532f8:/# apt install click-reviewers-tools
                  Reading package lists... Done
                  [...]
                  Processing triggers for libc-bin (2.23-0ubuntu10) ...
                  root@8fe1c0f532f8:/# click-review /clickdir/doniks.shorter_4.4_armhf.click 
                  ERROR: manifest malformed: unsupported field 'oldframework':
                  [...]
                  
                  
                  1 Reply Last reply Reply Quote 0
                  • H Offline
                    hummlbach
                    last edited by hummlbach 6 Mar 2018, 21:42 3 Jun 2018, 21:35

                    @arubislander Tell Brian in the openstore telegram group for example and give your click package to him.
                    @doniks Just do the sudo apt-get install click-reviewers-tools command outside the container. And then run it click-review also outside. UPDATE: okay, or like that πŸ™‚ ideally you could set it up with clickable some how s.t. clickable was doing the work inside the container for you - and you would never see it from the inside again... Badum tssss πŸ™‚

                    A 1 Reply Last reply 3 Jun 2018, 21:53 Reply Quote 1
                    • A Offline
                      arubislander @hummlbach
                      last edited by 3 Jun 2018, 21:53

                      @hummlbach said in Updating apps to 16.04:

                      @arubislander Tell Brian in the openstore telegram group for example and give your click package to him.

                      Thanks @hummlbach. Turns out it was some .cpp code I had added to test a feature, but it was superfluous, so I deleted it and now all is well.

                      πŸ‡¦πŸ‡Ό πŸ‡³πŸ‡± πŸ‡ΊπŸ‡Έ πŸ‡ͺπŸ‡Έ
                      Happily running Ubuntu Touch
                      Google Pixel 3a (20.04 DEV)
                      JingPad (24.04 preview)
                      Meizu Pro 5 (16.04 DEV)

                      D 1 Reply Last reply 3 Jun 2018, 22:08 Reply Quote 0
                      • D Offline
                        doniks @arubislander
                        last edited by 3 Jun 2018, 22:08

                        modules:composer.user_said_in, @arubislander, Updating apps to 16.04

                        @hummlbach said in Updating apps to 16.04:

                        @arubislander Tell Brian in the openstore telegram group for example and give your click package to him.

                        Thanks @hummlbach. Turns out it was some .cpp code I had added to test a feature, but it was superfluous, so I deleted it and now all is well.

                        Are you saying that you got your click to pass the click-review and then you could upload it?

                        A 1 Reply Last reply 3 Jun 2018, 22:16 Reply Quote 0
                        • A Offline
                          arubislander @doniks
                          last edited by 3 Jun 2018, 22:16

                          @doniks No, my click package passed the click-review from the outset.
                          I am saying that removing the c++ code caused the message to go away when uploading it to the open store.
                          It seems that even when your click package passes the click-review, you still need to have it reviewed by someone from the openstore, before getting it submitted.

                          πŸ‡¦πŸ‡Ό πŸ‡³πŸ‡± πŸ‡ΊπŸ‡Έ πŸ‡ͺπŸ‡Έ
                          Happily running Ubuntu Touch
                          Google Pixel 3a (20.04 DEV)
                          JingPad (24.04 preview)
                          Meizu Pro 5 (16.04 DEV)

                          1 Reply Last reply Reply Quote 1
                          • W Offline
                            Wendigo
                            last edited by 28 Aug 2018, 17:48

                            Is it possible to declare both frameworks for 15.04 and 16.04 together in one manifest.json so that the click package can be installed on both Ubuntu Touch versions?
                            The App itself is pure HTML5+JS so nothing needs to be compiled.

                            The current version looks like this:
                            {
                            "name": "sakawochi.wendigosoft",
                            "description": "The micro aquarium that fits into your pocket",
                            "architecture": "all",
                            "title": "Sakawochi",
                            "hooks": {
                            "sakawochi": {
                            "apparmor": "sakawochi.apparmor",
                            "desktop": "sakawochi.desktop"
                            }
                            },
                            "version": "0.2.11",
                            "maintainer": "Me <me@mymailbox.org>",
                            "framework" : "ubuntu-sdk-15.04.6"
                            }
                            Could I just add a "," or ";" in the framework field?

                            dobeyD 1 Reply Last reply 28 Aug 2018, 18:28 Reply Quote 0
                            • dobeyD Offline
                              dobey @Wendigo
                              last edited by 28 Aug 2018, 18:28

                              @wendigo No, you cannot do that. If the app works on both versions, and you want to keep uploading for both versions, I would suggest using the last 15.04 framework and apparmor 1.3 policy version, and just uploading the same package for both xenial and vivid.

                              However, rather than that, I'd suggest only uploading new versions for xenial. As I understand, the plan is to stop taking new app uploads for vivid soon, perhaps when OTA-5 is released.

                              1 Reply Last reply Reply Quote 2
                              • W Offline
                                Wendigo
                                last edited by 29 Aug 2018, 18:22

                                Thanks, I'll stay with framework 15.04 then and offer it for both versions on OpenStore.
                                Since not everyone will update to OTA-4 I want to support the old version until OTA-5 is out.

                                1 Reply Last reply Reply Quote 0
                                • costalesC Offline
                                  costales @DanChapman
                                  last edited by 12 Oct 2018, 13:33

                                  @danchapman Thanks for the tip. I removed the .py files and I was using this one import in last version:

                                  import io.thp.pyotherside 1.4

                                  Everything was working, but in the last update of Ubuntu Touch (2018-W40), the python side is not working.

                                  alt text

                                  In the last UT version I have the package libpython3.5:armhf, then I think the error is coming because the libpython3.4 doesn't exist. But... I'm just importing "io.thp.pyotherside 1.4", the crash (IMO) is coming from the pyotherside from the system (?).

                                  I tried import io.thp.pyotherside 1.5, but same result.

                                  Any help please? Thanks in advance!

                                  1 Reply Last reply Reply Quote 0
                                  • G gwengui referenced this topic on 11 Mar 2022, 20:19
                                  • First post
                                    Last post