Package Details: nodejs-imapnotify-git r39.f886715-1

Git Clone URL: https://aur.archlinux.org/nodejs-imapnotify-git.git (read-only, click to copy)
Package Base: nodejs-imapnotify-git
Description: Execute scripts on new messages using IDLE imap command
Upstream URL: https://github.com/titibandit/node-imapnotify
Licenses: MIT
Conflicts: nodejs-imapnotify
Submitter: yourealwaysbe
Maintainer: None
Last Packager: yourealwaysbe
Votes: 3
Popularity: 0.000000
First Submitted: 2015-01-10 19:01 (UTC)
Last Updated: 2023-10-28 10:56 (UTC)

Latest Comments

« First ‹ Previous 1 2

Rhinoceros commented on 2016-09-10 13:06 (UTC)

I get the following error when I install. (1/1) installing nodejs-imapnotify-git warning: directory permissions differ on /usr/bin/ filesystem: 755 package: 777 It's odd, because the package's usr/bin seems to have normal permissions (755). Maybe I don't understand this error…

yourealwaysbe commented on 2016-08-14 17:18 (UTC) (edited on 2016-08-14 17:18 (UTC) by yourealwaysbe)

@tealeaf -- do you still have this issue? I just tried it and had no problems. Apologies for the delay in responding.

tealeaf commented on 2016-08-01 12:00 (UTC) (edited on 2016-08-01 12:01 (UTC) by tealeaf)

I haven't seen this specifically mentioned here, although there seem to be a few related issues around the web. I installed this fine about a week ago, but now when I run a package update, or reinstall from scratch, I get to the: "==> Starting package()..." line, and npm sits there using up about a quarter of my CPU without progressing. I've run the relevant line from the PKGBUILD manually and it hangs on the first package install: "[..................] | normalizeTree: sill install loadCurrentTree" From a quick search, it seems that this is a known issue related to installing packages locally, but I haven't found if there is a well-known solution.

yourealwaysbe commented on 2015-10-04 16:34 (UTC)

Thanks, i've added this to make depends. The warning I think is benign and I don't know how to stop npm adding the references. It comes from npm installing dependencies locally. A better solution would be to create arch packages for all the dependencies, fit which I think there needs to be a better solution than me spending my afternoon making arch packages... (Maybe improving npm2arch.)

Rhinoceros commented on 2015-09-29 12:46 (UTC)

This package also needs npm to build, and has the warning: ==> WARNING: Package contains reference to $pkgdir

« First ‹ Previous 1 2