Arch Linux User Repository

The issue seems fixed upstream now. Thank you!

Hi smrdelv,

this may be related to https://github.com/brrd/abricotine/issues/318. Does the bug still persist? Does any of the other two abricotine packages work for you? (See https://aur.archlinux.org/packages/abricotine and https://aur.archlinux.org/packages/abricotine-bin.)

Best

Frank

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/135110.084662:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.

[651189:0608/135111.536027:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!

[651189:0608/135120.570232:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!

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

Best

Frank

@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.

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.

Best

Frank

@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.

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

git is missing as makedepends

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.