![]() |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Mb more polite would be to add a clutch to servicecontrol to check pebbled status and stop it if alive?
Or to add conflict statement to the service unit |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
Quote:
|
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Quote:
From systemd's manpage: "If a unit has a Conflicts= setting on another unit, starting the former will stop the latter and vice versa". This sounds much like the current situation: either pebbled is running, or rockpool, but you don't know which one. I don't know if this kind of conflict resolution can be resolved using a systemd unit configuration. |
Re: [Announce] Rockpool - Pebble daemon for Sailfish
Ok, so here is the logs when I start rockpoold from the command line : pastebin.com/p4brZPED .
If we take a look at the end, we can read that the new version is detected, but the internal status about available update is set to false. And with the calls from qdbus, I have the same results than before. Maybe because my version number has an unexpected format rockpool can't define if my version is the latest or not ? Edit : I did this with the 0.5-1 version |
All times are GMT. The time now is 11:11. |
vBulletin® Version 3.8.8