hakansv / ais-vd_pi Goto Github PK

@leamas
Thanks for the "updates-templates README". Following that a lot ci are built.
There's a fail on macOS due to some, what I understand, "commercial" issue. They want me to buy a "Performance plan"

Windows, Appveyor, is now on its way. I tried to get it going following "https://github.com/Rasbats/managed_plugins/wiki/Appveyor".
But I think I got errors?:
'Warning: CLOUDSMITH_API_KEY is not available, giving up.'
'Metadata: ais-vd-1.1-msvc-10.0.14393.xml'
'Tarball: ais-vd-1.1.30+1.cc37b73_msvc-10.0.14393-win32.tar.gz'
'Version: 1.1.30+1.cc37b73'
py ..\ci\git-push
No $GIT_REPO found, cannot push to git repo.
Build success

I'm trying to fix the API key and repo but I'm stuck here, see pict: I don't know what to enter. In cloudsmith I see a GPG and a RSA key but no API? What repo do they want? The wiki refers to rasbats/plugin.git but that sounds not good?

If you've the time I'm grateful but it can be more when we come to PIM when I'm already lost here??

As the heading says. Have a look at ShipDriver to see how the icon is added to the catalog list of installed plugins.

Hi Hakan,
I was able to do a small test this afternoon in the local AIS workshop.
The most important findings:
eta date: the ais is only using month and year. So no need for setting the year
eta time: Same the seconds are not used.
Every time the tap/page is opened/reopened there should be a new read request call being send, to make sure up to date data is viewed.
(If you change something now on the AIS itself, the data in the plugin is not updated.

Test was done on an "Trueheading" dual inland/solas AIS.
WKR Dirk

The README states that the overall license is GPL version 2 or later a. k. a. GPLv2+. However, here is some files which are GPLv3+. At least in shipdriver there is also files with licenses which are not compatible with GPLv2.

The basic solution to this is to declare the overall license to GPLv3+. It fits all the requirements.

I suggest that you look into shipdriver's README which has a section on copyright and licensing. If it's ok with you I think it can be used also here. In any case, do not change any license marking in a source file which is not copyrighted by you only, it's a legal disaster.

Not seeing this in the input screen. Has this been considered?

Seems that some catalog checksums does not match actual contents. In the plugins directory:

$  tools/check-metadata-urls  metadata/ais-vd-1.8.*
.....................C....C....C...........

3 errors detected

Checksum errors:

metadata/ais-vd-1.8.2-android-arm64-A64-16.xml: ais-vd-1.8.2_android-arm64-16-arm64.tar.gz
        metadata checksum: '40a2fdb9677eb26d5e19fd57c29c94f4750be3ac8f030e5c7f3ae0fbf35be8d6'
        computed checksum: '6586884bfa1df070f572593670cbddecf5ecbcb2df49bb2ff3ee206901dca42f'
metadata/ais-vd-1.8.2-darwin-wx32-10.xml: ais-vd-1.8.2_darwin-wx32-10-x86_64.tar.gz
        metadata checksum: '1faea89195b87c21829d824ad3639840f190a864d6e5db7984a02da7dbcf918b'
        computed checksum: 'bac0635d208d98d1bf3eb5b935a1253702f01fe66c3eecf6951c43d53e448ba0'
metadata/ais-vd-1.8.2-debian-A32-11.xml: ais-vd-1.8.2_debian-11-armhf.tar.gz
        metadata checksum: '9bbd8196daa73951f8e56746c5deb11b038eb18abdde5913000259939b26b4db'
        computed checksum: '642a732a071388b4befb59fd9e9aa02d182562172ba3d65bc458fffde7def06a'

@leamas
Although the push is tagged the Tarball again has the Git number?
Uploading ais-vd-1.4.0+21.305ed06_msvc-10.0.14393-win32.tar.gz:
create mode 100644 metadata/ais-vd-1.4-msvc-10.0.14393.xml
Could a Tag be done in various ways?

C:\Builds\OCPN\ais-vd_pi>git tag -a -m "Version 1.4.0" 1.4.0
C:\Builds\OCPN\ais-vd_pi>git push origin master

Buster build
Win build