-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TP 1.0.237 does not build all supported OS #312
Comments
Additional Information: Also see old plugins Issue posting OpenCPN/plugins#804 (comment) |
aarch64: Debian package: No explanation to missing plugins. This is a pretty good technique to see what plugin metadata is missing. Also see OpenCPN/OpenCPN#2986 (reply in thread) https://docs.google.com/spreadsheets/d/1_xQJ4gIGIp0rlexZTMdIkxrLMKKYzKQ7UzbCkGQ_IG4/htmlview |
Trying to figure out how to build flatpak-aarch64-22.08-arm64 In circleci/config.yml
and at the top of config.yml add
|
From Shipdriver v3.2.3 Cloudsmith shipdriver-prod LATER: Mike advised that the current shipdriver template is SD3.2.4-beta3 I have checked those metadata and they are the same as SD3.2.3 I think we can use these for the results that we need in TP Template. Then using Climatology 1.5.5.2 metadata that has been built in Cloudsmith for comparision DEBIAN 12 BOOKWORMShipDriver-sd3.2.3-debian-12.xml
climatology_pi-1.5.5.2-debian-x86_64-12-bookworm.xml
ShipDriver-sd3.2.3-debian-A32-12.xml
climatology_pi-1.5.5.2-debian-armhf-12-bookworm-armhf.xml
ShipDriver-sd3.2.3-debian-A64-12.xml
climatology_pi-1.5.5.2-debian-arm64-12-bookworm-arm64.xml
FLATPAK 22.08ShipDriver-sd3.2.3-flatpak-22.08.xml
climatology_pi-1.5.5.2-flatpak-x86_64-22.08-flatpak.xml
ShipDriver-sd3.2.3-flatpak-A64-22.08.xml
climatology_pi-1.5.5.2-flatpak-aarch64-22.08-flatpak.xml MISSING!!!in climatology_pi in circleci/config.yml
in circleci/config.yml
When I look at the build for "build-flatpak-arm64:" starting at line 538
Maybe this would be a better example to use, as it is using "resource_class: arm.medium" line which is more current for circleci! https://circleci.com/docs/using-arm/ If we do that, that would be changed to be
I think maybe this last revision would the be better one to add. What do you think? |
I decided to add to circleci/config.yml the following:
at Line 556 with some reorganization of existing builds
I changed the Climatology version to 1.5.5.3 and commited and pushed. Now how to get it tested? |
I have asked for testing in the Cruiser Forum's Climatology thread |
I will try to test today. |
Climatology v1.5.5.3 for flatpak/aarch64 imports, loads, and runs just fine by live test. Related note: There really is no reason at all to build flatpak 20.08. SDK 20.08 is long gone, unavailable. O58 requires SDK 22.08. So no reason to ask users to test a plugin built on 20.08. |
Great thanks Dave. Is there any reason to test the Debian 12 Bookworm, or should I just assume it works? Bram hasn't tested or advised yet. I think I will comment out the two flatpak 2008 builds. |
I will try to get to debian 12 test tonight. |
Closing. Done. Thanks! |
Later 8/1/2023 fixed Jammy. |
It appears that we are missing the following metadata, from each plugin built with TP 1.0.237 Template. Many users are reporting that TP Plugins are missing and there is a study done that shows the certain OS are missing.
From the TP Template Table
For example Climatology_pi 1.5.5 + TP1.0.237 was recently built and resulted in this list of metadata:
climatology-metadata-result-list.txt
More Detail
Filename (can be anything as it is not used) | Target (most important) |
climatology_pi-1.5.5.0-debian-arm64-wx32-12-bookworm-arm64.xml uses
<target>debian-wx32-arm64</target>
climatology_pi-1.5.5.0-debian-arm64-wx32-12-bookworm-arm64.xml uses
<target>debian-wx32-armhf</target>
climatology_pi-1.5.5.0-debian-x86_64-12-bookworm.xml uses
<target>debian-wx32-x86_64</target>
All three seem to have a "-wx32" in the target. Is this correct?
Also Is it possible to make the last filename have -wx32 ? Like this?
climatology_pi-1.5.5.0-debian-wx32-x86_64-12-bookworm.xml
so that it is easy to determine which files are for O5.6.2 and O5.8.2?
The text was updated successfully, but these errors were encountered: