Package Details: abricotine-git latest-1

Git Clone URL: (read-only, click to copy)
Package Base: abricotine-git
Description: A markdown editor with inline preview
Upstream URL:
Licenses: GPL3
Conflicts: abricotine
Provides: abricotine
Submitter: seifferth
Maintainer: seifferth
Last Packager: seifferth
Votes: 0
Popularity: 0.000000
First Submitted: 2019-11-20 19:08 (UTC)
Last Updated: 2022-05-22 16:34 (UTC)

Latest Comments

smradlev commented on 2022-07-02 09:33 (UTC)

The issue seems fixed upstream now. Thank you!

seifferth commented on 2022-06-09 18:27 (UTC) (edited on 2022-06-09 18:28 (UTC) by seifferth)

Hi smrdelv,

this may be related to Does the bug still persist? Does any of the other two abricotine packages work for you? (See and



smradlev commented on 2022-06-08 17:54 (UTC) (edited on 2022-06-08 17:54 (UTC) by smradlev)

Not sure if this is a bug with abricotine, or if it's a packaging issue. However, Abricotine shows an unresponsive blank window. In the terminal, I get:

Error while loading localization data: Error: EACCES: permission denied, open '/home/bjdcf/.config/Abricotine/app/lang/en.json'

libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)

[651189:0608/] InitializeSandbox() called with multiple threads in process gpu-process.

[651189:0608/] GetVSyncParametersIfAvailable() failed for 1 times!

[651189:0608/] GetVSyncParametersIfAvailable() failed for 2 times!

seifferth commented on 2022-05-22 17:39 (UTC)

Well, in that case, thanks a lot for your help. I very much appreciate it.



yochananmarqos commented on 2022-05-22 17:17 (UTC)

@seifferth: See VCS package guidelines

The only reason why I noticed is because I had signed up for release notifications and I was curious what was new. I'll probably never use this program, I was just bored. Anyway, I built it but it didn't run properly. I didn't look further into why and I'm no longer following the project.

seifferth commented on 2022-05-22 16:27 (UTC)

Hi yochananmarqos,

thanks for pointing me to npm pack. I was indeed quite lost on how to build the package. Since you seem to be quite at home with building abricotine, would you like to take over maintenance of the three packages? I'd be more than happy to add you as a Co-Maintainer, or to orphan the packages so you can adopt them.

Regarding the pkgver. I kind of dislike putting the most recent pkgver of *-git packages into the PKGBUILD. Putting any actual pkgver in the PKGBUILD means that the AUR has the wrong pkgver as soon as there's another commit to the repository in question. With "latest", it's at least clear that the pkgver inside the PKGBUILD is just a placeholder.

Anyway, if you would want to take over (co-)maintenance of the packages, you could just put whatever you prefer into the pgver ;) which would be completely fine with me.



yochananmarqos commented on 2022-05-22 15:58 (UTC)

@seifferth: This does not require rpm to build. Run npm pack, not npm dist as there's no reason to build a .deb and .rpm.

Run makepkg -od to populate the pkgver and push the changes. latest is not a valid pkgver.

seifferth commented on 2021-12-30 10:29 (UTC)

@FabioLolix: You're right, thanks. I added it.

FabioLolix commented on 2021-12-23 21:22 (UTC)

git is missing as makedepends

seifferth commented on 2019-11-21 12:39 (UTC)

Note: The current git version can't be built with the latest version of node due to problems with the node-spellchecker dependency. Building with nodejs-lts-erbium seems to work at the moment, however. Consider using nodejs-lts-erbium as your version of node if you want to build this package. I won't add it to the dependencies, however, since I hope this problem with node-spellchecker will be solved soon and we can build with the latest version again.

seifferth commented on 2019-11-21 12:00 (UTC)

Thanks for the comment. I updated pkgver as well as the provides array in both abricotine-git and abricotine-bin.

I am not sure if all the dependencies from the Debian control file are actually needed, though. Abricotine runs well without any kde dependencies on my machine, for instance, so it would probably be a bad idea to add them as real dependencies. I would want to check which of these can be made optdepends before adding them. If you figure out wich of the dependencies are actually needed, let me know. Otherwise, I'll look into it once I find time for it.

yochananmarqos commented on 2019-11-20 21:22 (UTC) (edited on 2019-11-20 21:23 (UTC) by yochananmarqos)

Please follow VCS package guidelines:

pkgver() {
    cd "$srcdir/abricotine"
    printf "%s" "$(git describe --long --tags | sed 's/\([^-]*-\)g/r\1/;s/-/./g')"

abricotine provides and conflicts with itself and does not need a provides() and conflicts() array. Since this package and abricotine-bin are variations, they both need to contain abricotine in provides() and conflicts().

This requires pandoc for the File > Run Task > Export with Pandoc function. It should be added to optdepends().

The dependencies according to the Debian control file are: gtk3 libnotify nss libxss libxtst xdg-utils trash-cli kde-cli-tools kdebase-runtime gvfs pulseaudio alsa-lib with gnome-keyring lsb-release as optional. About the first half of them make sense, but the latter half do not. Also strange that pandoc isn't mentioned.