We have moved to a new Sailfish OS Forum. Please start new discussions there.
1

pkcon fatal error 'file ... not found on medium ...' [answered]

asked 2016-01-26 20:17:51 +0300

yajo gravatar image

I tried to update my packages via 'pkcon update' but I got this error: "Fatal error: File './noarch/droid-system-packager-0.1.8-10.3.1.jolla.noarch.rpm' not found on medium 'https://store-repository.jolla.com/releases/2.0.1.7/jolla-hw/adaptation-qualcomm-sbj/armv7hl/?credentials=store' ". I can install repositories via Warehouse and apps via the Jolla Store. What can I do?

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by JSEHV
close date 2016-02-01 17:56:16.776403

Comments

Are you actually running 2.0.1.7?

objectifnul ( 2016-01-26 23:40:31 +0300 )edit

2 Answers

Sort by » oldest newest most voted
3

answered 2016-01-26 23:14:53 +0300

Keto gravatar image

Usually you don't need to, and should not, update the system packages via pkcon update. If you really need to, make sure to run pkcon refresh first, so that the repository meta data is up to date.

In this case the meta data is not up to date, as that is a wrong package version for that release.

If you are trying to update from 2.0.0.10 via command line, I strongly recommend not to, unless you know what you are doing and/or are willing to accept the fact that you might end up having to do a factory reset. If you have problems with the system update from the graphical user interface, please describe the issue you are having there and maybe those can be solved instead.

edit flag offensive delete publish link more

Comments

I did pkcon refresh and now I can update and install packages. Thank you!

yajo ( 2016-01-27 14:42:48 +0300 )edit
0

answered 2016-01-26 21:30:53 +0300

objectifnul gravatar image

Probably same issue here: https://together.jolla.com/question/127698/pkcon-refresh-repomdxml-not-found/

Please check and flag this post as duplicate if issue solved.

edit flag offensive delete publish link more

Comments

Not the same issue, you can see that from the repository URL, it has correct release... Assuming the device is currently running 2.0.1.7

Keto ( 2016-01-26 22:58:03 +0300 )edit

You may be right, unless 2.0.1.7 is used as default release number when /etc/ssu/ssu.ini wrongly stipulates "release=latest" instead of, say, 2.0.0.10

So I'd suggest @yajo to check anyway (ssu s), as it's easy and fast.

objectifnul ( 2016-01-26 23:12:28 +0300 )edit

Question tools

Follow
1 follower

Stats

Asked: 2016-01-26 20:17:51 +0300

Seen: 834 times

Last updated: Jan 26 '16