Scott Williams

I get this no matter what with the recent passman update (on nc15). It was working fine until the recent passman update yesterday. Now the app no longer connects and...

In my case, it looks like when I upgraded Nextcloud last, Passman was disabled because of the version not supported. When I updated Passman, it did not become re-enabled automatically,...

> Really, the gopkg.in idea is good, but if the service doesn't respond, that a SPOF for thouthands of projects. Totally agree. I wonder if it's feasible to backup these...

For what it's worth, we are running a mix of Alma, CentOS Stream, and RHEL and are using a common playbook for all of them from EL7-9 and everything seems...

Sure. I can do that on Monday (assuming I remember to check back here then).

My apologies - it appears that I did not, in fact, remember to check back. If I get a moment today, I'll update update our playbook and try it against...

I had a spare moment and updated the playbook to point to that repo for EL9 hosts and it works! Tested the playbook out against an AlmaLinux 9 node and...

I'm also having this on node v16.11.1, npm 8.0.0, node-gyp v8.2.0. This workaround worked for me: > Same errors using inotify-1.4.6, node v14.2.0, npm 6.14.5, node-gyp 6.1.0. > > The...

It looks like the fix is simply to update bindings to 1.5.0. Simply updating that in the package.json and it now installs fine without needing to inject the rebuild.

I'm not sure how this is working now anyway? I'm in the USA with en_US and I'm still seeing metric measurements. Besides, I know plenty of people who live in...