-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installation of Rockpool on SailfishOS 4.5.0.16 fails #107
Comments
You're installing a version intended for 4.4. You can either build the master from here, or add the community OBS repo. But you'll need QtConnectivity which was removed from Sailfish but I've also built in my OBS. |
please take a look at openrepos site, i complained there a lot, described what i did and it didn't work. anyway, i edited the file which i got via, as recommended on openrepos:
doing then
results in
well that can only happen if i comment out what was written in the repo file, found it in
still after that the rockpool is not able to detect the pebble classic i use. |
I'm not sure what you've done here, but the openrepos-abranson repo is completely separate from my OBS repo, which should be added separately with the 'ssu ar' command. It's best to use ssu's config, as that will configure the zypp backend. Editing zypp config manually might go wrong. If you're running an older version of SailishOS, such as on a community port, then the version on OBS probably wouldn't work as the dependencies will be wrong as you found with quazip. |
oh thank you! can you try to use the default openrepos config then? with that, and the command on openrepos to install, i am not able to install the rockpool.
can you double check if the repo works? |
Ah I see the problem. I think when I wrote those instructions, I assumed people would already have a previous version installed, and so 'zypper dup', which just performs an upgrade, would work. You should use 'zypper in rockpool' I guess. You should remove the openrepos repository if you're using OBS. I don't think they'll clash, but it's possible. |
thank you! however... i removed the OBS repo which i manually added and:
as i understand this should not happen. if i install from obs repo by having this config:
then it installs fine, but is not able to see the peeble classic watch. even though the watch is paired. and it is not able to open bluetooth settings from the app. |
Ok, I think you might be on an older version of sailfish then. The OBS is built against the latest. Glad you got it installed anyway. Did you check the pairing for 'LE'? What's the name of the paired device? |
no no, i am not on an older version. the device is pebble classic. i doubt it has le. let me connect to it and see again. |
and sailfishos updates says i am on 4.5.0.21 |
i am only able to install it from obs, not from openrepos. but then it doesn't see the paired watch. and the app is refusing to open bluetooth settings. |
That should just open the bluetooth page of the Settings app. What device name does the watch show on there? I think all the pebbles supported LE by the last firmware. |
That version its picking up is the old one built for SFOS 4.4, from openrepos. So that explains what's going on there. You're better off sticking to OBS and removing the openrepos repository completely. |
hello. so added the repo:
then trying to install:
os is the latest! can you please check? may it be you are too sure that the repo is in perfect condition? (again if i edit the repo file and add obs build, it will install and then fail to work, but you say it should install from openrepos!) |
ok i made it work from the obs. changed baseurl line to
then installed, by refreshing the cache. it has some warnings after install
upon startup it was not able to recognize the paired watch but then i restarted the app and it started to see it. so now it works, thank you. |
On upgrading to 4.5.0.16 the updater warned that Rockpool might conflict with this new version, so I uninstalled it prior updating. After updating, trying to install Rockpool 1.15 using Storeman fails. Same error (of course) as by using
pkcon
:I don't know if this would be the only issue, but it is the first blocking one when trying to install.
The text was updated successfully, but these errors were encountered: