| Git Clone URL: | https://aur.archlinux.org/joplin.git (read-only, click to copy) |
|---|---|
| Package Base: | joplin |
| Description: | A note taking and to-do application with synchronization capabilities - Desktop |
| Upstream URL: | https://joplinapp.org/ |
| Keywords: | markdown note notetaking productivity |
| Licenses: | MIT |
| Groups: | joplin |
| Conflicts: | joplin-desktop-electron |
| Submitter: | masterkorp |
| Maintainer: | masterkorp |
| Last Packager: | masterkorp |
| Votes: | 262 |
| Popularity: | 1.48 |
| First Submitted: | 2018-04-18 16:33 (UTC) |
| Last Updated: | 2024-07-29 19:54 (UTC) |
According to https://wiki.archlinux.org/index.php/.SRCINFO
Pushing an edited PKGBUILD to the AUR without also updating its .SRCINFO will cause the AUR to serve stale metadata.
.SRCINFO files may be generated using makepkg.
$ makepkg --printsrcinfo > .SRCINFO
Please make the necessary change soon.
I get this error:
failed to parse joplin: Line 30: key "pkgbase" can not occur after pkgbase or pkgname: pkgbase = joplin
@NutTool This should be fixed as of the update about 8 hours ago. This PKGBUILD doesn't use the npm package (which doesn't contain the desktop client) or the AppImage (which doesn't contain the terminal client). Instead it builds both from source.
The build process for the upstream is a little bit in flux at the moment and a change broke this package.
There appears to be an issue with the way npm is being run. I mistakenly filed a bug upstream: https://github.com/laurent22/joplin/issues/2263
Workaround for the current issue with .SRCINFO:
Clone AUR files from Git, remove the top block in .SRCINFO defining the old version of the package, makepkg -si and install manually. This should allow yay updates to proceed normally since it will not have to upgrade the package. yay seems to want to overwrite the .SRCINFO even if you make changes to it in your cache.
Maintainer simply needs to remove the duplicate block and push new manifest and then everything should be groovy.
I'm sorry but I am getting the same error :: Parsing SRCINFO (1/1): joplin failed to parse joplin: Line 30: key "pkgbase" can not occur after pkgbase or pkgname: pkgbase = joplin
And @louix in the .SRCINFO even if I remove the bottom (or the top one), it still throws off the same error (it's like it overwrites the .SRCINFO file when I try to install it with yay)
Also, gconf should be removed from dep list.
@ruigomes
I don't know why, but there are two "versions" of Joplin in .SRCINFO. Remove the bottom (old) one and it works.
I'm getting an error while trying to install this package:
:: Parsing SRCINFO (1/1): joplin failed to parse joplin: Line 30: key "pkgbase" can not occur after pkgbase or pkgname: pkgbase = joplin
I don't know what the problem is but AUR and yay still suggest the latest version still being 175. Chaotic not being built, either.
Pinned Comments
masterkorp commented on 2021-12-27 11:30 (UTC) (edited on 2021-12-27 11:32 (UTC) by masterkorp)
Hello everyone,
There was been several difficulties upgrading the Joplin due to major changes in the build system upstream.
I have finnally got version 2.6.10 working with pacthes, but remenber:
You may need to remove your src/ folder before using this version
The patches are still not perfect, you must say yes to a prompt
I will continue working on this later today, but its usable and stable, please remenber you can always report issues on the github repository.
Regards, Alfredo Palhares
masterkorp commented on 2020-12-24 19:58 (UTC) (edited on 2020-12-24 20:00 (UTC) by masterkorp)
Hello everyone,
I will be renaming the packages to its final form.
Also, please for problems with the package, please open an issue on the Github repo, its really hard to provide support on the comments section, you can also email me.
If you have problems with the
check()function, just run makepkg with the--nocheckflag.Thank you for your patience. Regards, Alfredo Palhares