Error with repository after update to 5.0.0.62

Bug Reports
1

REPRODUCIBILITY: always
OS VERSION: 5.0.0.62
HARDWARE: Xperia 10-II
UI LANGUAGE: German

DESCRIPTION:

Error with the repository “customer-jolla” since the update to 5.0.0.62. The first part is probably missing here:

https://releases.jolla.com/...

How can I fix this?

STEPS TO REPRODUCE:

  1. ssu lr

EXPECTED RESULT:

`# ssu lr
Enabled repositories (global):

Enabled repositories (user):
…`

MODIFICATIONS:

  • Chum
  • Patchmanager
2

try ‘ssu ur’ as root

3

‘ssu ur’ executes as root. The command ran without errors, but did not produce any other output.
Unfortunately, this did not correct the incorrect repository.

4

Yeah ssu ur just updates repos, you probably need to remove repo and then readd it, but if it will work, no clue
edit: maybe editing the file itself that contains the broken url is the way?

5

Can you tell me where I can find this file?

6

Unfortunately, this global repository cannot be deleted with either zypper or ssu.

7

What does the file /usr/share/ssu/features.d/customer-jolla.ini contain?

It should have this in it (and more)

[repositories-release]
customer-jolla = %(releaseRepoBaseURL)/features/
%(release)/customers/jolla/%(arch)/

8

It looks like this for me:

[repositories-release]
customer-jolla = %(releaseProtocol)://%(releaseDomain)/features/%(release)/customers/jolla/%(arch)/
9

Great, after this change it works.

Unfortunately, I initially commented out the old line out of stupidity. Now I have a 2nd repository that I can’t delete:

# ssu lr
Enabled repositories (global): 
 - #customer-jolla   ... :///features/5.0.0.62/customers/jolla/aarch64/

Can you please tell me how I can delete this global repository?

10

The only entry I could find on this is here:
/etc/zypp/repos.d/ssu_#customer-jolla_release.repo

Unfortunately, this is created again and again with # ssu ur. Where can I delete it?

11

Heh sounds like you’re having fun. Might have somehow got into /etc/ssu/ssu.ini maybe?

12

No, unfortunately this repo is not listed here. Where else can I look?
You can’t call it fun directly. But you learn something in the process. But I have to realize that this is easier solved in Debian.

13

Clear the ssu cache, as root

rm /var/cache/ssu/*

That should get rid of the “comented out” repo. Apparently the parser does not treat # properly as comment.

14

Also from which version did you update to 5.0.0.62, and did the update have any issues?

As it’s a bit weird that the /usr/share/ssu/features.d/customer-jolla.ini had the old URL template in it.

15

From version 4.6.0.15 to 5.0.0.62 and, as has been the case for many versions, with “sfos-upgrade”.

Unfortunately, I had forgotten to provide enough storage space. As a result, not all updates were carried out.

Notice: Do you want to upgrade SailfishOS from 4.6.0.15 to 5.0.0.62? (y/N) y

Notice: For troubleshooting issues with the upgrade proper, please consult https://docs.sailfishos.org/Support/Help_Articles/Updating_Sailfish_OS/#troubleshooting

- Stopping aliendalvik.service
Warning: The unit file, source configuration file or drop-ins of aliendalvik.service changed on disk. Run 'systemctl daemon-reload' to reload units.

- Setting SSU in release mode to SailfishOS release 5.0.0.62
Changing release from 4.6.0.15 to 5.0.0.62
Your device is now in release mode!

- Fetching and installing the SailfishOS upgrade from 4.6.0.15 to 5.0.0.62 (this may take a while):
REFRESHING CACHE AND DOWNLOADING PACKAGES
[99 %] [Download] aliendalvik 2.1.0-1.7.1.jolla: [100 %]
Error: File './aarch64/harbour-storeman-0.7.0-1.21.1.jolla.aarch64.rpm' not found on medium 'https://repo.sailfishos.org/obs/home:/olf:/harbour-storeman/5.0.0.62_aarch64/'
Finished transaction (status=2, runtime=745765ms)
UPGRADE NOT COMPLETE - Retry 1 of 9
Waiting 1 seconds before retry.
REFRESHING CACHE AND DOWNLOADING PACKAGES
Downloading: 0%
Error: File './aarch64/harbour-storeman-0.7.0-1.21.1.jolla.aarch64.rpm' not found on medium 'https://repo.sailfishos.org/obs/home:/olf:/harbour-storeman/5.0.0.62_aarch64/'
Finished transaction (status=2, runtime=273517ms)
UPGRADE NOT COMPLETE - Retry 2 of 9
Waiting 3 seconds before retry.
REFRESHING CACHE AND DOWNLOADING PACKAGES
Finished transaction (status=1, runtime=275352ms)
UPGRADING SYSTEM
[50 %] [Install] droid-system-pdx201 0.2.1-1.7.1.jolla: [50 %]
Error: Subprocess failed. Error: RPM failed: Command exited with status 2.
History:
 - warning: /var/cache/pk-zypp-cache/packages/adaptation0/aarch64/droid-system-pdx201-0.2.1-1.7.1.jolla.aarch64.rpm: Header V3 RSA/SHA256 Signature, key ID 47394f23: NOKEY
        installing package droid-system-pdx201-0.2.1-1.7.1.jolla.aarch64 needs 84MB more space on the / filesystem

Finished transaction (status=2, runtime=377933ms)
UPGRADE NOT COMPLETE - Retry 3 of 9
Waiting 3 seconds before retry.
REFRESHING CACHE AND DOWNLOADING PACKAGES
Finished transaction (status=1, runtime=211950ms)
UPGRADING SYSTEM
Finished transaction (status=2, runtime=454ms)

NO UPDATES FOUND. Try again later.

Notice: After rebooting, do not miss to run post_sfos-upgrade

I then freed up enough disk space and restarted the update with:

sfos-upgrade

I then reinstalled Storeman manually. This was probably not found automatically due to the change in the version number (it is now only called “5.0_aarch64/”). The subsequent restart was executed without errors.

16

I’m not at all sure, but could this topic also be related to the error I have with Storeman, since 5.0.0.62 upgrade on my X10III? Error says…

‘Can’t access given URL’

…nothing more! I don’t know how to seek what URL, or why.

17

There is already a topic for this issue.

18

Thanks, I should have known.

19

Now I had some time to test again. I have emptied the directory “/var/cache/ssu”. However, the files are created again via “ssu ur” with the same content as before. “ssu lr” still lists the commented out repo. Where else can I search?