Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
app-doc/geeknote: URI replace to my fork - previous repo is abandoned
Signed-off-by: Vitaly Zdanevich <[email protected]>
- Loading branch information
bebb60e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You forgot to update
metadata.xml
.Also you created this commit four minutes after replacing evernote3 with evernote2 upstream (vitaly-zdanevich/geeknote@b6e2849).
Later, you restrict tests for this ebuild but it seems that you haven't setup tests for your fork[1] nor do the original upstream tests seem to work for you[2].
Instead of forking and updating this package's sources prematurely, you could have also patched the original source in the ebuild (and maybe open a PR upstream so that more people benefit from your improvements).
Please correct me, if my assumptions are wrong. These changes just appear very rushed to me.
open issue at the time of writing:
[1] vitaly-zdanevich/geeknote#1
[2] jeffkowalski/geeknote#140
bebb60e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, metadata.xml updated 378987b
bebb60e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, no automated tests now :(
But after hours of investigation I found how to fix the Geeknote - and I did it, I did manual test - I can see notes content in my terminal. I checked it on two computers.
Nobody response on the original repo :(
For example this PR is open in 2023 jeffkowalski/geeknote#139
bebb60e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left a message about my fork - so author will see it jeffkowalski/geeknote#142
bebb60e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What fixes the change from the official evernote3 to the unofficial evernote2?
Adding python-oauth2 and evernote2 is problematic, given that the first one is officially deprecated (in favour of oauthlib) and the second is abandoned. An easy solution would be to revert vitaly-zdanevich/geeknote@b6e2849 and revert the commits adding python-oauth2 and evernote2.
bebb60e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Evernote/evernote-sdk-python@master...JackonYang:evernote2:master
Is it a drop-in replacement?
So Geeknote will stop work with official evernote3 Python SDK.
bebb60e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The evernote3 upstream is https://github.com/Evernote/evernote-sdk-python3, not the one you used to show that diff. Please check if geeknote works with evernote3.
I don't know.
bebb60e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It already was with evernote-sdk-python-3 - failing on every operation, I filled an issue for them https://github.com/Evernote/evernote-sdk-python3/issues/41
bebb60e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see. Thank you.
bebb60e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oauthlib
works with geeknote without changing of anything! 1810aefbebb60e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awesome! Then tomorrow I will proceed to masking python-oauth2 for removal if you agree
bebb60e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @stkw0 and @vitaly-zdanevich for figuring this out :)
Also sorry Vitaly about the whole paragraph about these changes being rushed. Who am I to judge, if I didn't really test it and if it works just fine.