@jimbojim I've tested the package through a regular install and clean build with both working without any issues. Looking at the error it also doesn't seem related to the package, but more likely with your local install. If the issue persists you might find more luck posting it on the Arch forums.
Search Criteria
Package Details: boostnote 0.11.15-2
| Git Clone URL: | https://aur.archlinux.org/boostnote.git (read-only) |
|---|---|
| Package Base: | boostnote |
| Description: | Open source note-taking app for programmers |
| Upstream URL: | https://boostnote.io/ |
| Keywords: | electron productivity |
| Licenses: | |
| Submitter: | rokt33r |
| Maintainer: | clone1612 |
| Last Packager: | clone1612 |
| Votes: | 51 |
| Popularity: | 1.058775 |
| First Submitted: | 2016-04-11 13:01 |
| Last Updated: | 2019-04-14 08:20 |
Dependencies (5)
- electron (electron-wayland)
- nodejs (nodejs-git, nodejs-0.12, nodejs6-bin, nodejs-lts-boron, nodejs-lts-carbon, nodejs-lts-dubnium)
- git (git-git) (make)
- grunt-cli (make)
- npm (npm53, npm4, nodejs6-bin) (make)
Required by (0)
Sources (7)
clone1612 commented on 2019-04-17 07:18
jimbojim commented on 2019-04-16 21:04
This is failing to build for me:
693 error Error while executing: 3693 error /usr/bin/git ls-remote -h -t git://github.com/adobe-webplatform/eve.git 3693 error 3693 error fatal: unable to connect to github.com: 3693 error github.com[0: 192.30.253.112]: errno=Connection refused 3693 error github.com[1: 192.30.253.113]: errno=Connection refused 3693 error 3693 error 3693 error exited with error code: 128 3694 verbose exit [ 1, true ]
clone1612 commented on 2019-04-14 08:28
@SirJson Thanks for that patch! It took a bit longer to fix the package as it's not compatible with Electron 4 (currently available in the Arch repo's) so I had to fix that too. Everything should now be fixed with these patches, let me know if you experience any additional/new issues.
SirJson commented on 2019-04-13 20:47
Until they release a new version that builds I stitched together a patch from an upstream commit that fixes the problem:
Commit: https://github.com/BoostIO/Boostnote/commit/0131bbbbed660926eace28b2b6e9c2f17f34dbb4
My patch: https://gist.github.com/SirJson/9b39dc5889ab3565f41b69107d76002b
captn3m0 commented on 2019-04-12 22:25
Currently broken because of https://github.com/BoostIO/Boostnote/issues/2969
clone1612 commented on 2018-12-18 08:38
@nix6839 Thanks for the notice! I'm watching releases on Github but got no notification there. Nonetheless I've updated the package to v0.11.12!
nix6839 commented on 2018-12-18 04:49
v0.11.12 is out!
ToKrCZ commented on 2018-11-16 17:43
Hello, v0.11.11 has been released and this time it seems to be properly tagged on github, so you should be able to build without any issues hopefully. Thanks in advance!
SirJson commented on 2018-10-27 17:29
If someone absolutely needs to build v0.11.10 right now he can try my script:
https://github.com/SirJson/boostnote-builder
I made it because I needed Boostnote on a system without Arch Linux. The script is based on the PKGBUILD that I found here but I thought why not upgrade the version to v0.11.10 as well.
The installer will make a user local installation (everything stays in your home directory) so it shouldn't clash with any packages. But as I said only if you absolutely need the newest version right now. Using the AUR is usually the better option here.
Also there shouldn't be that much of a difference between 0.11.9 and 0.11.10.
mapcode.mind commented on 2018-10-20 19:12
Regarding the update to v0.11.10: I can't update this package until the release is tagged on the main repository (https://github.com/BoostIO/Boostnote/issues/2513).
saw that just now, the tag is still at 0.11.9.
Edit : But, why can't this package be updated? the code is sitting right there. just saying cause they have marked your issue as improvement request.
Pinned Comments
clone1612 commented on 2018-06-13 06:04
Just an FYI on certain warnings appearing during the installation:
Warning about optional dependencies -> Bug in npm ignoring the --no-optional flag (https://github.com/npm/npm/issues/17633)
Reference to $srcdir ... -> Again unwanted behaviour in npm which saves absolute paths in the package.json file (https://github.com/npm/npm/issues/10393). These warnings can safely be ignored since package.json is not used after installation.
Security alerts -> Upstream issue, I'll try looking into it and fix things where possible