as usual... (repositories after SFOS release)

Question

6

as usual... (repositories after SFOS release)

asked 2020-04-29 11:52:34 +0200

objectifnul

9370 ●150 ●203 ●224

updated 2020-04-29 12:39:39 +0200

As usual when a new Sfos release is published but not applied yet (I prefer waiting a bit before doing so), most Openrepos updates cannot be installed, due to missing components in Jolla repositories (example: "File './droms/audioflingerglue-0.0.13-1.9.1.jolla_0.0.13_1.9.2 not found on medium ‘https://store-repository.jolla.com/releases/3.2.1.20/jolla-hw/adaptation-qualcomm-t5121/armv/hl/?credentials=store")

Is there a hint to circumvent this? (except premature upgrade of course)

edit retag flag offensive close delete

Comments

1

Could you add a bit more descriptive heading. (Edit: removed guesses to posters feelings :) )

miqu ( 2020-04-29 12:31:02 +0200 )edit

2

This is a somewhat known issue. As soon as SFOS tells you that "new upgrade is available" you can't manipulate packages until you have actually installed the upgrade. It has something to do with the upgrade mechanism internals. And it is the reason I only check dor updates manually.

Direc ( 2020-04-30 16:49:49 +0200 )edit

Could you add a bit more descriptive heading. (Edit: removed guesses to posters feelings :) )
miqu ( 2020-04-29 12:31:02 +0200 )edit
This is a somewhat known issue. As soon as SFOS tells you that "new upgrade is available" you can't manipulate packages until you have actually installed the upgrade. It has something to do with the upgrade mechanism internals. And it is the reason I only check dor updates manually.
Direc ( 2020-04-30 16:49:49 +0200 )edit

Answer 1

8

answered 2020-04-29 12:43:54 +0200

coderus

22985 ●253 ●337 ●370

https://coderus.openrepos...

updated 2020-04-29 12:44:02 +0200

keep calm

and

devel-su pkcon refresh

edit flag offensive delete publish link

Answer 2

2

answered 2020-04-29 16:00:01 +0200

olf
10393 ●104 ●201 ●158

updated 2020-04-29 16:01:10 +0200

Related / one reason for strange package management effects (when using an older release of SailfishOS):
[Bug] /usr/libexec/sailfish-osupdateservice osupdate-check sets ssu re

Workarounds are described there, which alleviate the fundamental issue.
But sometimes (e.g. right now, since SailfishOS 3.3.0 was released, installing or updating any RPM complains about audioflingerglue-0.0.13-1.9.1.jolla_0.0.13_1.9.2 not found) executing pkcon refresh is still necessary for installing and updating RPMs (e.g., from OpenRepos) successfully.

edit flag offensive delete publish link

Comments

1

Very interesting, thanks. But the workaround (by user instead of Jolla) is definitely unacceptable, as the bug was described (and tracked by Jolla) one year ago.

objectifnul ( 2020-04-29 16:37:28 +0200 )edit

Answer 3

1

answered 2020-04-29 12:34:44 +0200

MarkusKA

31 ●1 ●2

I often experienced your issue after installing a new release of Sailfish. The solution was, that I executed pkcon refresh as root or sudo pkcon refresh via terminal application or via ssh access to my phone (XA2 Plus).

edit flag offensive delete publish link

Comments

1

I did (via PackRefresh). Didn't fix the issue.

EDIT: actually it does, but only for a short while. The issue is back a couple of minutes later.

objectifnul ( 2020-04-29 12:40:54 +0200 )edit

Answer 4

0

answered 2020-04-29 12:45:40 +0200

coderus

22985 ●253 ●337 ●370

https://coderus.openrepos...

btw, seems your upgrade wasn't smooth? why 3.2.1.20 in repo?

check output of ssu lr and ssu re

ssu re should return 3.3.0.16

if not, then do ssu re 3.3.0.16 && version --dup

edit flag offensive delete publish link

Comments

2

As I explained above, I did not yet upgrade SFOS for several reasons. I will do of course sooner or later, but not now. I know this issue will disappear after that. My question is: why are most Openrepos updates not possible every time a new OS release is available but not yet applied?

objectifnul ( 2020-04-29 12:56:03 +0200 )edit

interesting I noticed this as well a few weeks ago after the EA release.

well I think this is a question you might post at the maemo forums as OpenRepos is 3rd-party

rozgwi ( 2020-04-29 13:37:25 +0200 )edit

@rozgwi Indeed, and that's why I opted out early access.

objectifnul ( 2020-04-29 14:16:32 +0200 )edit

1

sfos-upgrade script from OpenRepos works just fine. I use it exclusively because I was never able to upgrade my X via the settings. It does plenty of state checking before it performs the upgrade and the post install script cleans up and does a refresh.

DrDweeb ( 2020-04-29 19:31:21 +0200 )edit

1

I agree, although this is off-topic.

objectifnul ( 2020-04-29 19:35:48 +0200 )edit

Accepted Answer

0

answered 2020-04-30 18:03:40 +0200

objectifnul

9370 ●150 ●203 ●224

updated 2020-04-30 19:35:47 +0200

Maybe because of this question, Jolla updated the release notes 3.3.0 (see https://together.jolla.com/question/222221/release-notes-330-rokua/#222221-notification-concerning-apps-from-open-repos)

I suggest to use the Storeman built-in option allowing to disable or remove all Openrepos repositories in one pass (instead of ssu). As there is also an option allowing to backup/restore them, I think it's the best option to prevent repository inconsistencies related with a system upgrade.

~~An other, more radical choice is to erase all Storeman data with Mashka advanced options (see https://openrepos.net/content/osetr/mashka)~~

edit flag offensive delete publish link

Comments

Deleting Storeman's data will not disable the subscribed OpenRepos repositories!

As this has been an issue with SailfishOS before 1.0.4, a good description how to dis- and reenable all OpenRepos repositories at the command line in a single pass (each) was already provided back then:
https://together.jolla.com/question/33581/how-to-disable-openrepos-repositories/?answer=33721#post-id-33721

Alternatively one may try to use Storeman to backup the list of installed applications from OpenRepos (includes repository infos), disable all OpenRepos repositories with Storeman, upgrade to SailfishOS 3.3.0 and read back the backup in Storeman (as you already mentioned).

olf ( 2020-04-30 19:12:55 +0200 )edit

as usual... (repositories after SFOS release)

Comments

5 Answers

Comments

Comments

Comments

Comments

Question tools

Stats

Related questions

as usual... (repositories after SFOS release)

Comments

5 Answers

Comments

Comments

Comments

Comments

Question tools

Public thread

Stats

Related questions