We have moved to a new Sailfish OS Forum. Please start new discussions there.
1 | initial version | posted 2020-05-07 14:41:52 +0200 |
Hello.
We are developing the application for the old SailfishOS release, 2, and were able to use previous targets to build our application for the target release.
In the latest SDK release I was able to setup old target via SDK Control Center. But when I go to the Updates and try to get updates for the installed target I see the following error:
Finished: Syncing tooling repos SailfishOS-2.2.1.18 - Exited with status 0
[|] Valid metadata not found at specified URL(s)
File '/repodata/repomd.xml' not found on medium 'https://releases.jolla.com/releases/2.2.1.18/jolla/i486/'
Error building the cache:
[|] Valid metadata not found at specified URL(s)
File '/repodata/repomd.xml' not found on medium 'https://releases.jolla.com/releases/2.2.1.18/sdk/i486/'
Error building the cache:
[|] Valid metadata not found at specified URL(s)
When trying to access specified URL via web-browser I see the 404 error from the CloudFront.
Is it possible that the repositories for old releases were not published on CloudFront?
2 | No.2 Revision |
Hello.
We are developing the application for the old SailfishOS release, 2, and were able to use previous targets to build our application for the target release.
In the latest SDK release I was able to setup old target via SDK Control Center. But when I go to the Updates and try to get updates for the installed target I see the following error:
Finished: Syncing tooling repos SailfishOS-2.2.1.18 - Exited with status 0
[|] Valid metadata not found at specified URL(s)
File '/repodata/repomd.xml' not found on medium 'https://releases.jolla.com/releases/2.2.1.18/jolla/i486/'
Error building the cache:
[|] Valid metadata not found at specified URL(s)
File '/repodata/repomd.xml' not found on medium 'https://releases.jolla.com/releases/2.2.1.18/sdk/i486/'
Error building the cache:
[|] Valid metadata not found at specified URL(s)
When trying to access specified URL via web-browser I see the 404 error from the CloudFront.
Is it possible that the repositories for old releases were not published on CloudFront?
Update
The concrete redirect from the CloudFront for me is the following: https://dvvwui2qyedk6.cloudfront.net/releases/2.2.1.18/sdk/i486/
3 | No.3 Revision |
Hello.
We are developing the application for the old SailfishOS release, 2, and were able to use previous targets to build our application for the target release.
In the latest SDK release I was able to setup old target via SDK Control Center. But when I go to the Updates and try to get updates for the installed target I see the following error:
Finished: Syncing tooling repos SailfishOS-2.2.1.18 - Exited with status 0
[|] Valid metadata not found at specified URL(s)
File '/repodata/repomd.xml' not found on medium 'https://releases.jolla.com/releases/2.2.1.18/jolla/i486/'
Error building the cache:
[|] Valid metadata not found at specified URL(s)
File '/repodata/repomd.xml' not found on medium 'https://releases.jolla.com/releases/2.2.1.18/sdk/i486/'
Error building the cache:
[|] Valid metadata not found at specified URL(s)
When trying to access specified URL via web-browser I see the 404 error from the CloudFront.
Is it possible that the repositories for old releases were not published on CloudFront?
Update
The concrete redirect from the CloudFront for me is the following: https://dvvwui2qyedk6.cloudfront.net/releases/2.2.1.18/sdk/i486/
Update #2
I was able to add target SailfishOS-2.2.0.29-armv7hl, but when trying to compile the project it provides several issues:
ldconfig: loadlocale.c:129: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed.
ldconfig: loadlocale.c:129: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed.
4 more lines like this and when it finally tries to compile the application, it breaks on the make step:
+ %qtc_make -j8
/var/tmp/rpm-tmp.n7PoPF: line 47: fg: no job control
error: Bad exit status from /var/tmp/rpm-tmp.n7PoPF (%build)
Bad exit status from /var/tmp/rpm-tmp.n7PoPF (%build)
4 | No.4 Revision |
Hello.
We are developing the application for the old SailfishOS release, 2, and were able to use previous targets to build our application for the target release.
In the latest SDK release I was able to setup old target via SDK Control Center. But when I go to the Updates and try to get updates for the installed target I see the following error:
Finished: Syncing tooling repos SailfishOS-2.2.1.18 - Exited with status 0
[|] Valid metadata not found at specified URL(s)
File '/repodata/repomd.xml' not found on medium 'https://releases.jolla.com/releases/2.2.1.18/jolla/i486/'
Error building the cache:
[|] Valid metadata not found at specified URL(s)
File '/repodata/repomd.xml' not found on medium 'https://releases.jolla.com/releases/2.2.1.18/sdk/i486/'
Error building the cache:
[|] Valid metadata not found at specified URL(s)
When trying to access specified URL via web-browser I see the 404 error from the CloudFront.
Is it possible that the repositories for old releases were not published on CloudFront?
Update
The concrete redirect from the CloudFront for me is the following: https://dvvwui2qyedk6.cloudfront.net/releases/2.2.1.18/sdk/i486/
Update #2
I was able to add target SailfishOS-2.2.0.29-armv7hl, but when trying to compile the project it provides several issues:
ldconfig: loadlocale.c:129: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed.
ldconfig: loadlocale.c:129: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed.
4 more lines like this and when it finally tries to compile the application, it breaks on the make step:
+ %qtc_make -j8
/var/tmp/rpm-tmp.n7PoPF: line 47: fg: no job control
error: Bad exit status from /var/tmp/rpm-tmp.n7PoPF (%build)
Bad exit status from /var/tmp/rpm-tmp.n7PoPF (%build)
I know the issues are not related one to another, but they both prevent using the old toolchains in the latest release.
5 | No.5 Revision |
Hello.
We are developing the application for the old SailfishOS release, 2, and were able to use previous targets to build our application for the target release.
In the latest SDK release I was able to setup old target via SDK Control Center. But when I go to the Updates and try to get updates for the installed target I see the following error:
Finished: Syncing tooling repos SailfishOS-2.2.1.18 - Exited with status 0
[|] Valid metadata not found at specified URL(s)
File '/repodata/repomd.xml' not found on medium 'https://releases.jolla.com/releases/2.2.1.18/jolla/i486/'
Error building the cache:
[|] Valid metadata not found at specified URL(s)
File '/repodata/repomd.xml' not found on medium 'https://releases.jolla.com/releases/2.2.1.18/sdk/i486/'
Error building the cache:
[|] Valid metadata not found at specified URL(s)
When trying to access specified URL via web-browser I see the 404 error from the CloudFront.
Is it possible that the repositories for old releases were not published on CloudFront?
Update
The concrete redirect from the CloudFront for me is the following: https://dvvwui2qyedk6.cloudfront.net/releases/2.2.1.18/sdk/i486/
Update #2
I was able to add target SailfishOS-2.2.0.29-armv7hl, but when trying to compile the project it provides several issues:
ldconfig: loadlocale.c:129: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed.
ldconfig: loadlocale.c:129: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed.
4 more lines like this and when it finally tries to compile the application, it breaks on the make step:
+ %qtc_make -j8
/var/tmp/rpm-tmp.n7PoPF: line 47: fg: no job control
error: Bad exit status from /var/tmp/rpm-tmp.n7PoPF (%build)
Bad exit status from /var/tmp/rpm-tmp.n7PoPF (%build)
The same behavior has been tested on 2.4.0 and 2.2.4 SDK releases. I was reported by my colleague that he was able to use this target on 18.07 release.
I know the issues are not related one to another, but they both prevent using the old toolchains in the latest release.
6 | retagged |
Hello.
We are developing the application for the old SailfishOS release, 2, and were able to use previous targets to build our application for the target release.
In the latest SDK release I was able to setup old target via SDK Control Center. But when I go to the Updates and try to get updates for the installed target I see the following error:
Finished: Syncing tooling repos SailfishOS-2.2.1.18 - Exited with status 0
[|] Valid metadata not found at specified URL(s)
File '/repodata/repomd.xml' not found on medium 'https://releases.jolla.com/releases/2.2.1.18/jolla/i486/'
Error building the cache:
[|] Valid metadata not found at specified URL(s)
File '/repodata/repomd.xml' not found on medium 'https://releases.jolla.com/releases/2.2.1.18/sdk/i486/'
Error building the cache:
[|] Valid metadata not found at specified URL(s)
When trying to access specified URL via web-browser I see the 404 error from the CloudFront.
Is it possible that the repositories for old releases were not published on CloudFront?
Update
The concrete redirect from the CloudFront for me is the following: https://dvvwui2qyedk6.cloudfront.net/releases/2.2.1.18/sdk/i486/
Update #2
I was able to add target SailfishOS-2.2.0.29-armv7hl, but when trying to compile the project it provides several issues:
ldconfig: loadlocale.c:129: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed.
ldconfig: loadlocale.c:129: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed.
4 more lines like this and when it finally tries to compile the application, it breaks on the make step:
+ %qtc_make -j8
/var/tmp/rpm-tmp.n7PoPF: line 47: fg: no job control
error: Bad exit status from /var/tmp/rpm-tmp.n7PoPF (%build)
Bad exit status from /var/tmp/rpm-tmp.n7PoPF (%build)
The same behavior has been tested on 2.4.0 and 2.2.4 SDK releases. I was reported by my colleague that he was able to use this target on 18.07 release.
I know the issues are not related one to another, but they both prevent using the old toolchains in the latest release.