similar to: CentOS Digest, Vol 140, Issue 1

Displaying 20 results from an estimated 5000 matches similar to: "CentOS Digest, Vol 140, Issue 1"

2016 Nov 18
0
Anaconda installer fails to install nodejs010 and npm due to dependency error
Hi, I have built dependent packages of nodejs010 and npm successfully using mock and copy these RPMS to our ISO, anaconada installer fails to install due to dependency errors: nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.noarch requires nodejs010-npm(readable-stream) < 2 nodejs010-nodejs-cmd-shim-2.0.0-2.el7.centos.noarch requires nodejs010-npm(graceful-fs) < 4
2016 Aug 31
1
NODEJS010-NPM is not getting installed due to dependency errors on Custom Centos ISO installation
Hi, I have built successfully all the dependent packages of nodejs010 and npm. I have used following command:- *rpmbuild --define 'scl nodejs010' --bb SPEC/name_of_spec.spec* Following is the list of RPMs cloned and built from GIT:- nodejs010-2.1-5.el7.centos.x86_64.rpm nodejs010-http-parser-2.0-6.20121128gitcd01361.el7.centos.x86_64.rpm
2017 Mar 29
0
Nodejs010 Packages giving unresolved dependency error when building the nodejs packages
Hi, I am trying to built an ISO with nodejs010 packages but when I run the command "repoclosure -a x86_64 -r <local-repository-name>" to check its further dependencies, it is giving unresolved dependencies error. Example: package: nodejs010-node-gyp-3.2.0-2.el7.centos.noarch from Harman (it's a local repo name) unresolved deps: npm(minimatch) < 0:4
2015 Dec 21
0
Announcing release for NodeJS 0.10 on CentOS Linux 7 x86_64 SCL
I am pleased to announce the immediate availability of version 0.10 of the NodeJS on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl $ sudo yum install nodejs010 $ scl enable
2015 Dec 21
0
Announcing release for NodeJS 0.10 on CentOS Linux 6 x86_64 SCL
I am pleased to announce the immediate availability of version 0.10 of the NodeJS on CentOS Linux 6 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl $ sudo yum install nodejs010 $ scl enable nodejs010
2015 Dec 22
0
CentOS-announce Digest, Vol 130, Issue 10
Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When
2016 Aug 31
2
group write permissions not being respected
So far, those look the same client: [root at mseas FixOwn]# getfacl /gdata/bibliography/Work/GroupBib/trunk/ getfacl: Removing leading '/' from absolute path names # file: gdata/bibliography/Work/GroupBib/trunk/ # owner: phaley # group: mseasweb # flags: -s- user::rwx group::rwx other::r-x server: [root at mseas-data2 ~]# getfacl /gdata/bibliography/Work/GroupBib/trunk/ getfacl:
2016 Aug 31
2
group write permissions not being respected
For example the directory /gdata/bibliography/Work/GroupBib/trunk/ can be written in by user phaley but not by other users who are member of the group mseasweb. The directory has permissions [root at mseas ~]# ls -lh /gdata/bibliography/Work/GroupBib total 12K drwxrwsr-x 4 phaley mseasweb 4.0K Aug 30 12:31 trunk The parent directory (/gdata/bibliography/Work/GroupBib) has permissions [root
2017 Mar 14
0
Strange behaviour of yum within %post in kickstart
Hi, (This is happening on CentOS 6) during a machine's kickstart I install several yum repositories which are contained in an RPM. During the %post phase I install an RPM which has a dependency to nodejs. That package with all of its dependencies can be found in EPEL. On the other hand I have the Softwarecollections repository, which also contains nodejs with the same version. Now nodejs
2014 May 30
3
nodejs, epel, SCL
Hello, ?With SCL and epel repositories enabled, some dependencies for the package name 'nodejs' get satisfied with libs from SCL which are placed in paths that are not part of my user's environment. Is there a method to make sure that nodeJS from epel dependencies are only satisfied from epel? For example, the http parser dependency gets satisfied by
2013 Jul 18
2
Puppetlabs Apt module: dependency cycle
Using ```puppetlabs/apt``` in a puppet provisioner for vagrant. the module is installed in puppet/modules and I''m getting a strange Dependency cycle error. the code in the manifest file: # Run apt-get update when anything beneath /etc/apt/ changes #taken from https://blog.kumina.nl/2010/11/puppet-tipstricks-running-apt-get-update-only-when-needed/ exec { "apt-get
2011 Jun 04
2
Weird paramterized issue
Im using a parameterized class in my site.pp: class development($user) { class{"basenode": user => $user} class{"nodejs": user => $user} include "coffeescript" include "ruby" } This class defines nodejs class that epects a user as input: class nodejs($user) { class {"nodejs::npm": user => $user} $node_ver =
2016 Aug 30
2
group write permissions not being respected
Hi We have just migrated our data to a new file server (more space, old server was showing its age). We have a volume for collaborative use, based on group membership. In our new server, the group write permissions are not being respected (e.g. the owner of a directory can still write to that directory but any other member of the associated group cannot, even though the directory clearly
2016 Jul 19
0
Announcing release of NodeJS 4 on CentOS Linux 7 x86_64 SCL
I am pleased to announce the immediate availability of NodeJS in version 4 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl $ sudo yum install rh-nodejs4 $ scl
2017 Nov 28
0
Announcing release of NodeJS 8 on CentOS Linux 7 x86_64
I am pleased to announce the immediate availability of NodeJS in version 8 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl-rh $ sudo yum install rh-nodejs8 $ scl enable
2016 Aug 31
2
CentOS 6 - logwatch report not in HTML format
On Mon, Aug 29, 2016 at 10:24 PM, Alexander Farber <alexander.farber at gmail.com> wrote: > No, I mean there is sometimes a variable for mail format too: The HTML formatting is a logwatch option, invoked through the logwatch.conf file. -- Arun Khan
2016 Aug 31
2
CentOS 6 - logwatch report not in HTML format
On Wed, Aug 31, 2016 at 7:58 AM, Alexander Farber <alexander.farber at gmail.com> wrote: > logwatch is run as cronjob. Let's take cron out of the picture. Invoking logwatch from an interactive shell -- no joy. The report still goes out in text format. -- Arun Khan
2018 Dec 11
0
Announcing release of NodeJS 10
I am pleased to announce the immediate availability of NodeJS in version 10 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: # 1. Install a package with repository for your system: $ sudo yum install
2016 Aug 31
0
CentOS 6 - logwatch report not in HTML format
logwatch is run as cronjob. On Wed, Aug 31, 2016 at 4:11 PM, Arun Khan <knura9 at gmail.com> wrote: > On Mon, Aug 29, 2016 at 10:24 PM, Alexander Farber > <alexander.farber at gmail.com> wrote: > > No, I mean there is sometimes a variable for mail format too: > > The HTML formatting is a logwatch option, invoked through the > logwatch.conf file. > > -- Arun
2016 Aug 31
0
CentOS 6 - logwatch report not in HTML format
You should have provided more info initially. "goes out in text format" might mean several things. On Wed, Aug 31, 2016 at 5:31 PM, Arun Khan <knura9 at gmail.com> wrote: > On Wed, Aug 31, 2016 at 7:58 AM, Alexander Farber > <alexander.farber at gmail.com> wrote: > > logwatch is run as cronjob. > > Let's take cron out of the picture. Invoking