Skip to content
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

fix getpPrivateApplicationLocation #31

Closed
rgleason opened this issue Jun 18, 2021 · 8 comments
Closed

fix getpPrivateApplicationLocation #31

rgleason opened this issue Jun 18, 2021 · 8 comments

Comments

@rgleason
Copy link
Owner

@filochard wrote about logbook at bottom of post.
OpenCPN/OpenCPN#2306 (comment)

@leamas can you take a look I. thought I had fixed this and pushed up to PIM.

@filochard are you sure you are using the updated PIM version?

Perhaps I got something wrong.

@rgleason rgleason changed the title Thank-you! getpPrivateApplicationLocation fix. getpPrivateApplicationLocation Jun 18, 2021
@rgleason rgleason changed the title fix. getpPrivateApplicationLocation fix getpPrivateApplicationLocation Jun 18, 2021
@leamas
Copy link

leamas commented Jun 18, 2021

@filochard: Which version are you using? What is the problem you see?

@filochard
Copy link

For watchdog I tried to update to 2.4.31.0 from the plugin manager
I get this
screen_20210618-135207
If I download it from :
https://cloudsmith.io/~opencpn/repos/watchdog-prod/packages/
I can update to 2.4.31.0
no change : the xml file is stored in the wrong directory
/home/myusername/.opencpn/plugins/watchdog/
instead of
/home/myusername/.var/app/org.opencpn.OpenCPN/config/opencpn/plugins/watchdog/

if I download it from
https://cloudsmith.io/~opencpn/repos/watchdog-beta/packages/
I can update to 2.4.31.1
then the xml file is always stored in a right place

Something wrong in the catalogue I think
And a wrong place for the tarball in the cloud

@leamas
Copy link

leamas commented Jun 18, 2021

@rgleason: This is yours to handle...

@leamas
Copy link

leamas commented Jun 18, 2021

I have tested 2..4.31 as built directly from source, and for me it worked just fine. So, as you say, this is most likely just some silly catalog issue (or rather build i. e., the build has not uploaded the tarball to the proper location). Let's leave this to Rick.

The open issue is about this plugin LogBookKonni. You seem to have mentioned it at the end of your post as problematic. My initial questions "Which version" and "What's the problem" was actually about LogBookKonni...

@filochard
Copy link

Sorry I was not clear in the end of this comment :
OpenCPN/OpenCPN#2306 (comment)
What I meant was that watchdog needed the same solution as what had been done to logbookkoni which works now (layouts installed in the right directory and txt files too)

@rgleason
Copy link
Owner Author

Good about logbook. Not to clear about what but I think alec fixed it.

1st sail this year back in 2-3 days and will update pim. Many thanks to @leamas @filochard

@leamas
Copy link

leamas commented Jun 18, 2021

Don't mention me here -- I don't have a single commit in LogBook... Seems that you fixed it yourself
.

@rgleason
Copy link
Owner Author

Closing. Done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants