Cant install myapp to nexus 5

asked 2017-07-07 20:34:20 +0200

qmmp123
1 ●1 ●1 ●2

updated 2019-01-28 10:07:19 +0200

jiit
2678 ●32 ●58 ●59

  admin

SFOS version: 2.0.4.13 Hi there! Sorry for my english. When I try to install myapp to nexus 5 I get this error

Error: nothing provides libQt5Core.so.5(Qt_5)

I googled this error and found similar problem But after this commands

ssu release 2.0.5.6
version --dup

I got this errors

[nemo@Sailfish ~]$ version --dup
REFRESHING CACHE AND DOWNLOADING PACKAGES
Refreshing: 71% (remaining: 6s)
Error: File '/repodata/repomd.xml' not found on medium 'http://repo.merproject.org/obs/nemo:/devel:/hw:/common/sailfishos_2.0.4.13/'

Finished transaction (status=2, runtime=22295ms)
UPGRADE NOT COMPLETE - Retry 1 of 9
Waiting 1 seconds before retry.
REFRESHING CACHE AND DOWNLOADING PACKAGES
Refreshing: 71% (remaining: 6s)
Error: File '/repodata/repomd.xml' not found on medium 'http://repo.merproject.org/obs/nemo:/devel:/hw:/common/sailfishos_2.0.4.13/'

Finished transaction (status=2, runtime=21093ms)
UPGRADE NOT COMPLETE - Retry 2 of 9
Waiting 3 seconds before retry.
REFRESHING CACHE AND DOWNLOADING PACKAGES
Refreshing: 71% (remaining: 6s)
Error: File '/repodata/repomd.xml' not found on medium 'http://repo.merproject.org/obs/nemo:/devel:/hw:/common/sailfishos_2.0.4.13/'

Finished transaction (status=2, runtime=20924ms)
UPGRADE NOT COMPLETE - Retry 3 of 9
Waiting 3 seconds before retry.
REFRESHING CACHE AND DOWNLOADING PACKAGES
Refreshing: 71% (remaining: 6s)
Error: File '/repodata/repomd.xml' not found on medium 'http://repo.merproject.org/obs/nemo:/devel:/hw:/common/sailfishos_2.0.4.13/'

Finished transaction (status=2, runtime=21496ms)
UPGRADE NOT COMPLETE - Retry 4 of 9
Waiting 5 seconds before retry.
REFRESHING CACHE AND DOWNLOADING PACKAGES
Refreshing: 71% (remaining: 6s)
Error: File '/repodata/repomd.xml' not found on medium 'http://repo.merproject.org/obs/nemo:/devel:/hw:/common/sailfishos_2.0.4.13/'

Finished transaction (status=2, runtime=21112ms)
UPGRADE NOT COMPLETE - Retry 5 of 9
Waiting 5 seconds before retry.
REFRESHING CACHE AND DOWNLOADING PACKAGES
Refreshing: 71% (remaining: 6s)
Error: File '/repodata/repomd.xml' not found on medium 'http://repo.merproject.org/obs/nemo:/devel:/hw:/common/sailfishos_2.0.4.13/'

Finished transaction (status=2, runtime=21112ms)
UPGRADE NOT COMPLETE - Retry 5 of 9
Waiting 5 seconds before retry.
REFRESHING CACHE AND DOWNLOADING PACKAGES
Refreshing: 71% (remaining: 6s)
Error: File '/repodata/repomd.xml' not found on medium 'http://repo.merproject.org/obs/nemo:/devel:/hw:/common/sailfishos_2.0.4.13/'

Finished transaction (status=2, runtime=20908ms) UPGRADE NOT COMPLETE - Retry 6 of 9
Waiting 5 seconds before retry.
REFRESHING CACHE AND DOWNLOADING PACKAGES Refreshing: 71% (remaining: 6s) Error: File '/repodata/repomd.xml' not found on medium 'http://repo.merproject.org/obs/nemo:/devel:/hw:/common/sailfishos_2.0.4.13/'

Finished transaction (status=2, runtime=22036ms) UPGRADE NOT COMPLETE - Retry 7 of 9 Waiting 10 seconds before retry. REFRESHING CACHE AND DOWNLOADING PACKAGES Refreshing: 71% (remaining: 6s) Error: File '/repodata/repomd.xml' not found on medium 'http://repo.merproject.org/obs/nemo:/devel:/hw:/common/sailfishos_2.0.4.13/'

Finished transaction (status=2, runtime=21141ms) UPGRADE NOT COMPLETE - Retry 8 of 9 Waiting 20 seconds before retry. REFRESHING CACHE AND DOWNLOADING PACKAGES Refreshing: 71% (remaining: 6s) Error: File '/repodata/repomd.xml' not found on medium 'http://repo.merproject.org/obs/nemo:/devel:/hw:/common/sailfishos_2.0.4.13/'

Finished transaction (status=2, runtime=22157ms) UPGRADE NOT COMPLETE - Retry 9 of 9 Waiting 30 seconds before retry. REFRESHING CACHE AND DOWNLOADING PACKAGES Refreshing: 71% (remaining: 9s) Error: File '/repodata/repomd.xml' not found on medium 'http://repo.merproject.org/obs/nemo:/devel:/hw:/common/sailfishos_2.0.4.13/'

Finished transaction (status=2, runtime=53148ms) FINISHING

The upgrade could NOT be finished. Make sure you have a working Internet Connection and SSU is propertly set up. In case the repos are changing rapidly (e.g. during development), just restarting the upgrade might fix the issue.

REBOOT AT YOUR OWN RISK.