Discuss September 2016

discuss@lists.centos.org

118 participants
96 discussions

CentOS-announce Digest, Vol 139, Issue 1
by centos-announce-request＠centos.org 06 Sep '16

06 Sep '16

Send CentOS-announce mailing list submissions to centos-announce(a)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(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2016:1797 Moderate CentOS 6 ipa Security Update (Johnny Hughes) 2. CESA-2016:1809 Important CentOS 6 thunderbird Security Update (Johnny Hughes) 3. CESA-2016:1809 Important CentOS 7 thunderbird Security Update (Johnny Hughes) 4. CESA-2016:1797 Moderate CentOS 7 ipa Security Update (Johnny Hughes) 5. CEBA-2016:1782 CentOS 5 kernel BugFix Update (Johnny Hughes) 6. CEEA-2016:1780 CentOS 7 megaraid_sas Enhancement Update (Johnny Hughes) 7. CESA-2016:1809 Important CentOS 5 thunderbird Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 5 Sep 2016 21:43:35 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1797 Moderate CentOS 6 ipa Security Update Message-ID: <20160905214335.GA53161(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1797 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1797.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 9a76945f5e53fe3c46ba6b2e8d41153083e277ed1489e061e0362b367cf24d4c ipa-admintools-3.0.0-50.el6.centos.2.i686.rpm 6f680dcb53cac90df163ec295785294f0ec32f24b15597a5daca0313b08381ee ipa-client-3.0.0-50.el6.centos.2.i686.rpm 84e184732f6308d01aafb08ab5fb9a1ae598e8e7571ff3e0f3a1ffdf7ab7ea1e ipa-python-3.0.0-50.el6.centos.2.i686.rpm 07fef5c092bac45a50d3247960ecdc0dec541fbfbec477d3349e1448d35c14d6 ipa-server-3.0.0-50.el6.centos.2.i686.rpm 4d5b11679dc5e57df4fa0dc140286d0b9ef412427595428b34082022512b3d76 ipa-server-selinux-3.0.0-50.el6.centos.2.i686.rpm deeeed4c887d0e4e30d89488530783aa9753a5b745a4ecbe693871a48304acea ipa-server-trust-ad-3.0.0-50.el6.centos.2.i686.rpm x86_64: 587735bf88f12a0bafd20ee1a9705a95005bc96a0de2e38af2b7fda50000ef0e ipa-admintools-3.0.0-50.el6.centos.2.x86_64.rpm 031cba9a9b15305d4012ec302075d00775177f2b90edc81708d05e7d3eb6231f ipa-client-3.0.0-50.el6.centos.2.x86_64.rpm be36a599f91e5145e3bfe7f2667df00bc8ce3a687116faf44319b4aa489cb11a ipa-python-3.0.0-50.el6.centos.2.x86_64.rpm eb88f0ebfae6ab06720dd9e7fc39084f49be08e779348489881a89e784727ef6 ipa-server-3.0.0-50.el6.centos.2.x86_64.rpm 83f5893b4987c35cec70208fc24b6d4b791711b98c872af999ffd65174e7feb5 ipa-server-selinux-3.0.0-50.el6.centos.2.x86_64.rpm bafa5aff6a70875f2c61f6b98743d699e33ba416d14cfc8376fe9942c8455b3f ipa-server-trust-ad-3.0.0-50.el6.centos.2.x86_64.rpm Source: eedfa288be6cc62b86d9256c2858fcf24a0ee92f76ae69bed4c6138e3a1a651c ipa-3.0.0-50.el6.centos.2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Tue, 6 Sep 2016 00:52:40 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1809 Important CentOS 6 thunderbird Security Update Message-ID: <20160906005240.GA57754(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1809 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1809.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 160bf41d5398da8512e7fa77a05c3a0dc80d7360cfa79391a8a81cfc4ecb6352 thunderbird-45.3.0-1.el6.centos.i686.rpm x86_64: 6373b92e88b90d043376aa5d712bf272ad3ef57cdf869ffced7c8ab225c121e2 thunderbird-45.3.0-1.el6.centos.x86_64.rpm Source: 30a522d59cf4ea68f38a2abaeff0678b933f47ac3f24d488548a33d66c50d526 thunderbird-45.3.0-1.el6.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Tue, 6 Sep 2016 01:03:39 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1809 Important CentOS 7 thunderbird Security Update Message-ID: <20160906010339.GA611(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1809 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1809.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: b27f983a9dec3f17f00b47d9d7666b09f4cec07dda59f802698355cb03f7637f thunderbird-45.3.0-1.el7.centos.x86_64.rpm Source: 6212956c18c7e6d7dde1b6008ef6ce2ba4b4cbe1be20ab3a7df8760c9d64074d thunderbird-45.3.0-1.el7.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Tue, 6 Sep 2016 01:06:50 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1797 Moderate CentOS 7 ipa Security Update Message-ID: <20160906010650.GA738(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1797 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1797.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: a7723ce570b09c36f1ada06495f1f94a29da95d4c67fd0e65bef2b88887e3759 ipa-admintools-4.2.0-15.0.1.el7.centos.19.x86_64.rpm d87a6bb3956f5260d41dcedfe36a9baec7769896554203cb2aae40094f84d19f ipa-client-4.2.0-15.0.1.el7.centos.19.x86_64.rpm edef4178644b2c9563a267ffa829b27788e2835a4f3da1c99e41298ff181ddda ipa-python-4.2.0-15.0.1.el7.centos.19.x86_64.rpm 6e4ec8cea775914ea5901ca0cb79f11784382402a2d3dee3087c292e2941f47d ipa-server-4.2.0-15.0.1.el7.centos.19.x86_64.rpm 008c9b943528d60aac4f50114a3b414d969f3d8833a70d2384370b48d2c93501 ipa-server-dns-4.2.0-15.0.1.el7.centos.19.x86_64.rpm 4d05bc6e0bbb71e03c1b30875ab2753510885e2b31af15039c05c12960c30b4e ipa-server-trust-ad-4.2.0-15.0.1.el7.centos.19.x86_64.rpm Source: 02a7bacd4d9918c760425e5dbefd0f3fddfbbc7ea676f2d6e5ac05f62b689a49 ipa-4.2.0-15.0.1.el7.centos.19.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 5 Date: Tue, 6 Sep 2016 02:32:18 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:1782 CentOS 5 kernel BugFix Update Message-ID: <20160906023218.GA2750(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:1782 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1782.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 1cceade3db635e6bf40767b8aa889f606f9cd2dc520fb052a96b6e57238feaa0 kernel-2.6.18-412.el5.i686.rpm 8945438f684a6aa25b76fd80feb732b9ac3e255d04b58de5505564a7145bd3b5 kernel-debug-2.6.18-412.el5.i686.rpm 61d2a461ba59ac6e320467b30bf6c42e987404f38d66cb31a5dd79521d3b3687 kernel-debug-devel-2.6.18-412.el5.i686.rpm 72605760160a752047e16fd5df9ed9fe570adc9971cff8541cee85c0c8b46a53 kernel-devel-2.6.18-412.el5.i686.rpm 42f7cc1cbb5cef688e2ce0c2eb08762893388a62d82abf9c29e9177c925aa805 kernel-doc-2.6.18-412.el5.noarch.rpm 2d9bb3dec0d4fc5d10c0b0387f29548873e4a1f392a6ab6942d1b89aa59ff438 kernel-headers-2.6.18-412.el5.i386.rpm b4172316d3e8f8abf971e584ff1f6430608ecd3a39a1905eb100b863a326779b kernel-PAE-2.6.18-412.el5.i686.rpm e6ab24b639e50767707b7f12db2df390bd3ca890dfae45a1a3f8d3140c5fd72a kernel-PAE-devel-2.6.18-412.el5.i686.rpm cb983ecf3dfc441fab4fce2d37b3bf7f7ff5aac9fe540b7f9f2960314e62c54e kernel-xen-2.6.18-412.el5.i686.rpm 65ae34ecd9bea1bf2602db9a86c2c18cf092def5f66974c355ea406d6e1a141f kernel-xen-devel-2.6.18-412.el5.i686.rpm x86_64: 84f47ad942923cf26eee3b7d5b11f568432dd0254f4134e00e691e44a05ce487 kernel-2.6.18-412.el5.x86_64.rpm 05514dabf3ebedfdc73dac2f3a6b5fa225652a6b975466e5dcbfad6750600b77 kernel-debug-2.6.18-412.el5.x86_64.rpm ff51e7bcf97ce8d7e06ba182b887c027179d8b8f098ea27e4fce26b742735997 kernel-debug-devel-2.6.18-412.el5.x86_64.rpm ba7bb3a039d17b1b77c6b61d1bcb10a5b525d86409b5d62675f6e3050fd74491 kernel-devel-2.6.18-412.el5.x86_64.rpm 42f7cc1cbb5cef688e2ce0c2eb08762893388a62d82abf9c29e9177c925aa805 kernel-doc-2.6.18-412.el5.noarch.rpm 7fc9955692715dbdc376b44010bea114e71f4504c31174102edc4666242111bc kernel-headers-2.6.18-412.el5.x86_64.rpm 8e2b726c35e8abf898ba536ae46bd2d5dda07e05ccaabb20149e36cdbfe2a632 kernel-xen-2.6.18-412.el5.x86_64.rpm 69087d91bc243cbea186d77f15ed57b5f53da6871ab9fe2d8a71484bf7f6a04e kernel-xen-devel-2.6.18-412.el5.x86_64.rpm Source: 396e2d189ecfb2c31254e7d657e208ac3c9ea0e31f7ae399ca7a5f9b36b97495 kernel-2.6.18-412.el5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: JohnnyCentOS ------------------------------ Message: 6 Date: Tue, 6 Sep 2016 03:16:44 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2016:1780 CentOS 7 megaraid_sas Enhancement Update Message-ID: <20160906031644.GA4629(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2016:1780 Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-1780.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 3f942683663a5acf3ec76fbc4da33363451ff5778ea1da2dec382806510af15f kmod-megaraid_sas-06.811.02.00-1.el7_2.x86_64.rpm Source: 1433047acea21ed246eb8eaf21f0b6856722158687bdc521ab9a6466566d798d megaraid_sas-06.811.02.00-1.el7_2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 7 Date: Tue, 6 Sep 2016 03:19:56 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1809 Important CentOS 5 thunderbird Security Update Message-ID: <20160906031956.GA4578(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1809 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1809.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 4cb84a2e017f0e5ed15f2c76e633f1ed84c23d466fb11c856847cbd3e49a3533 thunderbird-45.3.0-1.el5.centos.i386.rpm x86_64: 5ef01b379661dcf482838ccac167aeb9fca091b6fa2cfab1ca0a0facf3d41523 thunderbird-45.3.0-1.el5.centos.x86_64.rpm Source: f6a805f44b19087570cae54f6790916279351bf878bd9f51f742bd7175803877 thunderbird-45.3.0-1.el5.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: JohnnyCentOS ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 139, Issue 1 ***********************************************

1 0

hacking grub to control number of retained kernels.
by Fred Smith 06 Sep '16

06 Sep '16

I've recently had this problem on two C7 systems, wherein when doing "yum update", I get a warning about /boot being low on space. both systems were installed using the partition size recommended by Anaconda, right now "df -h" shows /boot as 494M, with 79M free. I don't store unrelated crap on /boot, I assume that yum and/or grub will manage it for me. So, why, after over a year, is it running low on space on two different systems? Is there some location in /boot where junk piles up, but shouldn't, that I have to know about so I can clean it out? I see EIGHT initramfs files in /boot, two per kernel, same name but one has a kdump just before the .img suffix. do I need those for old kernels that I may or may not ever boot? (they're 30 to 50 MB each). For the moment I've edited /etc/grub.conf and changed installonly_limit from 4 to 3. (related question: do I need to manually remove the oldest kernel, having done this, or will yum/grub clean it up the next time there's a kernel to install?) thanks! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- I can do all things through Christ who strengthens me. ------------------------------ Philippians 4:13 -------------------------------

4 4

Centos7 kickstart & pxe
by johan.vermeulen7＠telenet.be 05 Sep '16

05 Sep '16

Hello All, I'm trying to get kickstart to work through pxe. So far I've set up dhcp server, tftp and so on. But it seems at some point I always get stuck because the iso file is write-protected. I've tried remounting it rw, and I 've dd the iso first, I then get EM not a block device. Any help would be appreciated. Greetings, J.

3 4

/etc/sysconfig/network HOSTNAME settings
by Walter H. 04 Sep '16

04 Sep '16

Hello, I found different ways to define the hostname ... this HOSTNAME="host.domain.tld" or this: HOSTNAME="host" DOMAIN="domain.tld" what is the correct way? Thanks, Walter

3 2

How do I install uwsgi + python 3?
by Yuri Kanivetsky 04 Sep '16

04 Sep '16

Hi, >From what I can see, epel doesn't have python 3's pip. But when I install python35u (ius) and uwsgi-python-plugin3, uwsgi's python doesn't seem to find virtual env's packages. When I install python34u (ius) and uwsgi-plugin-python3, I get a conflict. Am I doing anything wrong? Regards, Yuri

1 0

Re: [CentOS] Networking/routing issue
by tdukes＠palmettoshopper.com 03 Sep '16

03 Sep '16

-------- Original Message -------- Subject: Re: [CentOS] Networking/routing issue From: Ulf Volmer <u.volmer(a)u-v.de> Date: Sat, September 03, 2016 5:47 am To: centos(a)centos.org On 09/03/2016 01:31 PM, TE Dukes wrote: > Centos 6.8 server eth0 > 192.168.1.110 > gateway 192.168.1.111 > eth1 > 192.168.1.111 > gateway > 192.168.1.100 > | > | > Switch > other computers and devices > gateway 192.168.1.110 > > I want to send all internal traffic through 192.168.1.110, all external > traffic through 192.168.1.111, then back through 192.168.1.110. As far as i understand, you have two interfaces in the same subnet. This is usually a bad idea. best regards Ulf Volmer A few of the examples I tried, had them on different subnets. I will change that and see what happens. Thanks

1 0

Networking/routing issue
by TE Dukes 03 Sep '16

03 Sep '16

Hello, I've been working on this for over a week. I don't think its working the way it should. Here's what I'm trying to do: I have a Windstream dsl router with wireless > 192.168.1.100 | | Centos 6.8 server eth0 > 192.168.1.110 > gateway 192.168.1.111 eth1 > 192.168.1.111 > gateway 192.168.1.100 | | Switch > other computers and devices > gateway 192.168.1.110 I want to send all internal traffic through 192.168.1.110, all external traffic through 192.168.1.111, then back through 192.168.1.110. I did an iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE Issues: Outside connectivity for all other computers and devices only works if eth0 is also connected to the router, server works Iptraf shows no traffic on eth1 Hope I haven't confused you as I have thoroughly confused myself. TIA TE Dukes

3 3

Re: [CentOS] Network manager cannot connet to the Internet
by sunyeping 03 Sep '16

03 Sep '16

Hi, Earl, Thank you very much for your prompt response.There is no output for "ip route"I don't know what is my default gateway and how to check it? And how to check the device that I am connecting to? Best regards. Yeping------------------------------------------------------------------From:Earl A Ramirez <earlaramirez(a)gmail.com>Time:2016 Sep 3 (Sat) 18:38To:CentOS mailing list <centos(a)centos.org>Subject:Re: [CentOS] Network manager cannot connet to the Internet What is the output of ip route show, can you ping your gateway, first see if you can ping your default gateway and if you can't you will have to check the device that your are connecting to. -- Kind Regards Earl Ramirez _______________________________________________ CentOS mailing list CentOS(a)centos.org https://lists.centos.org/mailman/listinfo/centos

1 0

Re: [CentOS] CentOS Digest, Vol 140, Issue 1
by SUDHANSHU BHUTANI 02 Sep '16

02 Sep '16

On Thu, Sep 1, 2016 at 5:30 PM, <centos-request(a)centos.org> wrote: > Send CentOS mailing list submissions to > centos(a)centos.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.centos.org/mailman/listinfo/centos > or, via email, send a message with subject or body 'help' to > centos-request(a)centos.org > > You can reach the person managing the list at > centos-owner(a)centos.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of CentOS digest..." > > > Today's Topics: > > 1. Re: CentOS 6 - logwatch report not in HTML format (Arun Khan) > 2. Re: NODEJS010-NPM is not getting installed due to dependency > errors on Custom Centos ISO installation (Jim Perrin) > 3. Re: CentOS 6 - logwatch report not in HTML format > (Alexander Farber) > 4. Re: CentOS 6 - logwatch report not in HTML format (Arun Khan) > 5. Re: CentOS 6 - logwatch report not in HTML format > (Alexander Farber) > 6. Re: group write permissions not being respected (Gordon Messmer) > 7. Re: CentOS 6 - logwatch report not in HTML format (Arun Khan) > 8. Re: group write permissions not being respected (Pat Haley) > 9. Re: group write permissions not being respected (m.roth(a)5-cent.us) > 10. Re: group write permissions not being respected (Pat Haley) > 11. Re: group write permissions not being respected (Chris Murphy) > 12. Perl Unsafe Module Path Handling Directory Traversal > Vulnerability ( CVE-2016-1238) (Sidharth Sharma) > 13. Bind Vulnerability CVE-2016-2775 (Sidharth Sharma) > 14. Re: "Windows" share issue; access via smb:// fails, "mount -t > cifs" works (Toralf Lund) > 15. Re: Bind Vulnerability CVE-2016-2775 (James Pearson) > 16. Re: Bind Vulnerability CVE-2016-2775 (Mike Burger) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 31 Aug 2016 07:11:11 -0700 > From: Arun Khan <knura9(a)gmail.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] CentOS 6 - logwatch report not in HTML format > Message-ID: > <CAHhM8gCz6SDqu8i5aHkUU58Sb91cHdNKUy=J_rYP25X48gk22Q(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On Mon, Aug 29, 2016 at 10:24 PM, Alexander Farber > <alexander.farber(a)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 > > > ------------------------------ > > Message: 2 > Date: Wed, 31 Aug 2016 09:20:26 -0500 > From: Jim Perrin <jperrin(a)centos.org> > To: centos(a)centos.org > Subject: Re: [CentOS] NODEJS010-NPM is not getting installed due to > dependency errors on Custom Centos ISO installation > Message-ID: <a607d751-c5e7-91eb-9e81-b6cdb379ecfa(a)centos.org> > Content-Type: text/plain; charset=windows-1252 > > > > On 08/31/2016 03:48 AM, SUDHANSHU BHUTANI wrote: >> 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* > > You should really use mock, so that you don't have unintended libraries > from your build host included/linked/required in the resulting rpm. Thanks Jim for responding. I tried with mock configuration, but, not sure, i am still getting the same errors via repoclosre tool:- This directory has got all the RPMs formed by mock. [root@localhost YUM_CISCO_RPMS]# repoclosure -r Cisco-yum-dep-check Reading in repository metadata - please wait.... Checking Dependencies Repos looked at: 1 Cisco-yum-dep-check Num Packages in Repos: 1515 package: nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(readable-stream) < 0:2 package: nodejs010-nodejs-cmd-shim-2.0.0-2.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(graceful-fs) < 0:4 package: nodejs010-nodejs-columnify-1.3.2-3.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(strip-ansi) >= 0:2.0.0 package: nodejs010-nodejs-fstream-ignore-1.0.2-1.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(minimatch) < 0:3 package: nodejs010-nodejs-gauge-1.2.2-3.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(has-unicode) < 0:2 package: nodejs010-nodejs-init-package-json-1.9.1-1.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(promzard) >= 0:0.3.0 package: nodejs010-nodejs-npm-registry-client-7.0.8-1.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(retry) >= 0:0.8.0 nodejs010-npm(request) >= 0:2.47.0 nodejs010-npm(concat-stream) >= 0:1.4.6 package: nodejs010-nodejs-which-1.2.0-1.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(is-absolute) < 0:0.2 The only difference from my (for build of nodejs010-nodejs-which-1.2.0-1.el7.centos.noarch.rpm) build-log and http://cbs.centos.org/kojifiles/packages/nodejs010-nodejs-are-we-there-yet/… is following line:- *Requires: nodejs010-nodejs(engine) nodejs010-npm(delegates) nodejs010-npm(readable-stream)* - >> THIS IS FROM CBS mock log and following is my build log:- *Requires: nodejs010-nodejs(engine) nodejs010-npm(delegates) >= 0.1.0 nodejs010-npm(delegates) < 0.2 nodejs010-npm(readable-stream) >= 1.1.13 nodejs010-npm(readable-stream) < 2* I am not sure, why parsing of these version is defining a range, maybe its coming from package.json file. I feel, its related to nodejs010-build package which has root/usr/lib/rpm/nodejs010.req, i defined mock configuration like this:- config_opts['root'] = 'epel-7-x86_64' config_opts['target_arch'] = 'x86_64' config_opts['legal_host_arches'] = ('x86_64',) config_opts['chroot_setup_cmd'] = 'install @buildsys-build scl-utils-build nodejs010-build' Do they look good? Following is my build.log [sbhutani@localhost ~]$ cat nodejs-build/nodejs010- Display all 316 possibilities? (y or n) [sbhutani@localhost ~]$ cat nodejs-build/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.src.rpm/build.log Mock Version: 1.2.18 ENTER ['do'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'], chrootPath='/var/lib/mock/epel-7-x86_64/root'shell=FalseprintOutput=Falseenv={'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '}gid=135user='mockbuild'timeout=0logger=<mockbuild.trace_decorator.getLog object at 0x22e3390>uid=1000) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '} and shell False Building target platforms: x86_64 Building for target x86_64 Wrote: /builddir/build/SRPMS/nodejs-are-we-there-yet-1.0.4-1.el7.centos.src.rpm Child return code was: 0 Mock Version: 1.2.18 ENTER ['do'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'], chrootPath='/var/lib/mock/epel-7-x86_64/root'shell=FalseprintOutput=Trueenv={'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '}gid=135user='mockbuild'timeout=0logger=<mockbuild.trace_decorator.getLog object at 0x1772390>uid=1000) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '} and shell False Building target platforms: x86_64 Building for target x86_64 Wrote: /builddir/build/SRPMS/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.src.rpm Child return code was: 0 Mock Version: 1.2.18 ENTER ['do'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'], chrootPath='/var/lib/mock/epel-7-x86_64/root'shell=FalseprintOutput=Falseenv={'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '}gid=135user='mockbuild'timeout=0logger=<mockbuild.trace_decorator.getLog object at 0x142d390>uid=1000) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '} and shell False Building target platforms: x86_64 Building for target x86_64 Wrote: /builddir/build/SRPMS/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.src.rpm Child return code was: 0 ENTER ['do'](['bash', '--login', '-c', u'/usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'], chrootPath='/var/lib/mock/epel-7-x86_64/root'shell=Falseuid=1000env={'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '}gid=135user='mockbuild'timeout=0private_network=Truelogger=<mockbuild.trace_decorator.getLog object at 0x142d390>printOutput=False) Executing command: ['bash', '--login', '-c', u'/usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '} and shell False Building target platforms: x86_64 Building for target x86_64 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.cNqdgI + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf package + /usr/bin/gzip -dc /builddir/build/SOURCES/are-we-there-yet-1.0.4.tgz + /usr/bin/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd package + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + rm -rf node_modules + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.iiP8RP + umask 022 + cd /builddir/build/BUILD + cd package + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.IFmFuX + umask 022 + cd /builddir/build/BUILD + '[' /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64 '!=' / ']' + rm -rf /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64 ++ dirname /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64 + mkdir -p /builddir/build/BUILDROOT + mkdir /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64 + cd package + mkdir -p /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64/opt/rh/nodejs010/root/usr/lib/node_modules/are-we-there-yet + cp -pr package.json index.js /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64/opt/rh/nodejs010/root/usr/lib/node_modules/are-we-there-yet + /usr/lib/rpm/nodejs010-symlink-deps /opt/rh/nodejs010/root/usr/lib/node_modules + /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/BUILD/package /usr/lib/rpm/sepdebugcrcfix: Updated 0 CRC32s, 0 CRC32s did match. + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/brp-scl-compress /opt/rh/nodejs010/root + /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/brp-scl-python-bytecompile /usr/bin/python 1 /opt/rh/nodejs010/root + /usr/lib/rpm/brp-python-hardlink + /usr/lib/rpm/redhat/brp-java-repack-jars Processing files: nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.noarch Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.7DYIy5 + umask 022 + cd /builddir/build/BUILD + cd package + DOCDIR=/builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64/opt/rh/nodejs010/root/usr/share/doc/nodejs010-nodejs-are-we-there-yet-1.0.4 + export DOCDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64/opt/rh/nodejs010/root/usr/share/doc/nodejs010-nodejs-are-we-there-yet-1.0.4 + cp -pr README.md /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64/opt/rh/nodejs010/root/usr/share/doc/nodejs010-nodejs-are-we-there-yet-1.0.4 + exit 0 Finding Provides: /usr/lib/rpm/nodejs010.prov Finding Requires(interp): Finding Requires(rpmlib): Finding Requires(verify): Finding Requires(pre): Finding Requires(post): Finding Requires(preun): Finding Requires(postun): Finding Requires(pretrans): Finding Requires(posttrans): Finding Requires: /usr/lib/rpm/nodejs010.req Provides: nodejs010-nodejs-are-we-there-yet = 1.0.4-1.el7.centos nodejs010-npm(are-we-there-yet) = 1.0.4 Requires(rpmlib): rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 Requires: nodejs010-nodejs(engine) nodejs010-npm(delegates) >= 0.1.0 nodejs010-npm(delegates) < 0.2 nodejs010-npm(readable-stream) >= 1.1.13 nodejs010-npm(readable-stream) < 2 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64 Wrote: /builddir/build/RPMS/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.noarch.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.yi6hbn + umask 022 + cd /builddir/build/BUILD + cd package + /usr/bin/rm -rf /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64 + exit 0 Child return code was: 0 [sbhutani@localhost ~]$ Can any one catch difference between my build.log and CBS build.log. If hhorak is on this mailing list who actually built this package on CBS, can help? Appreciate your inputs. >> >> Following is the list of RPMs cloned and built from GIT:- >> > > <snip> > > >> >> *However, when we copy these RPMS to our ISO, anaconda installer fails >> to install due to dependency errors:-* > > > You should use the 'repoclosure' utility to make sure that you have met > all the dependencies of packages in the repo on your iso. > > > >> How is it possible, to get these errors, how come packages are not >> satisfying minimum dependency for working of NPM? > > > repoclosure should tell you. You may be missing something scl related. > > >> >> If i do yumdownloader for all these above RPMs from repo: [centos-sclo-rh] >> : http://mirror.centos.org/centos/7/sclo/x86_64/rh/nodejs010/), then i >> get following RPMs without "centos" name:- > > > Correct. This is an rpm macro change. by default the 'centos' is added > in there. > > >> >> *If i copy paste above RPMS to my custom ISO, then anaconda >> successfully installs these packages, without any errors* > > > This would suggest something is wrong with your build. See previous > statement about using mock vs rpmbuild. > > >> *What is there is these already built RPMs (taken from repo: [centos-sclo-rh] >> : http://mirror.centos.org/centos/7/sclo/x86_64/rh/nodejs010/) which >> is not there in my built RPMS?* > > That's kind of up to you to figure out, since we can't see your custom > built ones. > > >> Any pointers for this, as we feel, there is some inconsistency in the >> version available on git.centos.org/git/rpms/<name_of_pkg>.git ? > > More likely it's in your build method. > > > -- > Jim Perrin > The CentOS Project | http://www.centos.org > twitter: @BitIntegrity | GPG Key: FA09AD77 > > > ------------------------------ > > Message: 3 > Date: Wed, 31 Aug 2016 16:58:17 +0200 > From: Alexander Farber <alexander.farber(a)gmail.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] CentOS 6 - logwatch report not in HTML format > Message-ID: > <CAADeyWiMVpHh=CDZ6zi_OEq+5HwysoqTAOABDnM4mkYeFDhxYA(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > logwatch is run as cronjob. > > On Wed, Aug 31, 2016 at 4:11 PM, Arun Khan <knura9(a)gmail.com> wrote: > >> On Mon, Aug 29, 2016 at 10:24 PM, Alexander Farber >> <alexander.farber(a)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 >> _______________________________________________ >> CentOS mailing list >> CentOS(a)centos.org >> https://lists.centos.org/mailman/listinfo/centos >> > > > ------------------------------ > > Message: 4 > Date: Wed, 31 Aug 2016 08:31:28 -0700 > From: Arun Khan <knura9(a)gmail.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] CentOS 6 - logwatch report not in HTML format > Message-ID: > <CAHhM8gDhhgRNb1C2rKRdE+v8w_fEhBmCvarf3MxO=njxL7w3-g(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On Wed, Aug 31, 2016 at 7:58 AM, Alexander Farber > <alexander.farber(a)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 > > > ------------------------------ > > Message: 5 > Date: Wed, 31 Aug 2016 17:59:44 +0200 > From: Alexander Farber <alexander.farber(a)gmail.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] CentOS 6 - logwatch report not in HTML format > Message-ID: > <CAADeyWiYQ_TNjZHZ9af2x3TM_Lq+U9LE+y4aheb6BXV_TBwGaQ(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > 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(a)gmail.com> wrote: > >> On Wed, Aug 31, 2016 at 7:58 AM, Alexander Farber >> <alexander.farber(a)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 >> _______________________________________________ >> CentOS mailing list >> CentOS(a)centos.org >> https://lists.centos.org/mailman/listinfo/centos >> > > > ------------------------------ > > Message: 6 > Date: Wed, 31 Aug 2016 09:50:45 -0700 > From: Gordon Messmer <gordon.messmer(a)gmail.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] group write permissions not being respected > Message-ID: <8d10f9b1-0ed9-0217-ae0e-726acd1d9a87(a)gmail.com> > Content-Type: text/plain; charset=windows-1252; format=flowed > > On 08/30/2016 03:01 PM, Pat Haley wrote: >> 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 has group write permissions set > > > Use "getfacl" on both the client and server side to view the complete > permission set. What do those look like? > > > > ------------------------------ > > Message: 7 > Date: Wed, 31 Aug 2016 10:00:42 -0700 > From: Arun Khan <knura9(a)gmail.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] CentOS 6 - logwatch report not in HTML format > Message-ID: > <CAHhM8gBBc+i9VH=eiGM+K7ePerQbv4Nraa5ck7YMEixrhbzaoQ(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On Wed, Aug 31, 2016 at 8:59 AM, Alexander Farber > <alexander.farber(a)gmail.com> wrote: >> You should have provided more info initially. >> >> "goes out in text format" might mean several things. >> > > I don't know what you mean by "several things" > > In the context of logwatch the only options are HTML or TEXT. Please see my OP. > > Thanks for your assistance. > > -- Arun Khan > > > ------------------------------ > > Message: 8 > Date: Wed, 31 Aug 2016 13:11:09 -0400 > From: Pat Haley <phaley(a)mit.edu> > To: centos(a)centos.org > Cc: Steve Postma <SPostma(a)ztechnet.com> > Subject: Re: [CentOS] group write permissions not being respected > Message-ID: <8d59038f-3dbe-5bff-9673-fbada1d3f31c(a)mit.edu> > Content-Type: text/plain; charset=windows-1252; format=flowed > > > So far, those look the same > > client: > > [root@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@mseas-data2 ~]# 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 > > > On 08/31/2016 12:50 PM, Gordon Messmer wrote: >> On 08/30/2016 03:01 PM, Pat Haley wrote: >>> 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 has group write permissions set >> >> >> Use "getfacl" on both the client and server side to view the complete >> permission set. What do those look like? >> >> _______________________________________________ >> CentOS mailing list >> CentOS(a)centos.org >> https://lists.centos.org/mailman/listinfo/centos > > -- > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Pat Haley Email: phaley(a)mit.edu > Center for Ocean Engineering Phone: (617) 253-6824 > Dept. of Mechanical Engineering Fax: (617) 253-8125 > MIT, Room 5-213 http://web.mit.edu/phaley/www/ > 77 Massachusetts Avenue > Cambridge, MA 02139-4301 > > > > ------------------------------ > > Message: 9 > Date: Wed, 31 Aug 2016 14:04:28 -0400 > From: m.roth(a)5-cent.us > To: "CentOS mailing list" <centos(a)centos.org> > Subject: Re: [CentOS] group write permissions not being respected > Message-ID: > <b9abfd5a5a37f29bff085aae6174877f.squirrel(a)host290.hostmonster.com> > Content-Type: text/plain;charset=utf-8 > > Stupid question, and note I missed most of the earlier posts in this > thread: what are the permissions on the directory that this directory are > in? > > mark > > > > ------------------------------ > > Message: 10 > Date: Wed, 31 Aug 2016 15:06:25 -0400 > From: Pat Haley <phaley(a)mit.edu> > To: centos(a)centos.org > Subject: Re: [CentOS] group write permissions not being respected > Message-ID: <d9ac7e12-3283-ea9e-a5b0-5dcd8d27d87d(a)mit.edu> > Content-Type: text/plain; charset=windows-1252; format=flowed > > > 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@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@mseas ~]# ls -lh /gdata/bibliography/Work/ > total 8.0K > drwxrwsr-x 6 phaley mseasweb 4.0K Aug 30 14:01 GroupBib > > > > On 08/31/2016 02:04 PM, m.roth(a)5-cent.us wrote: >> Stupid question, and note I missed most of the earlier posts in this >> thread: what are the permissions on the directory that this directory are >> in? >> >> mark >> >> _______________________________________________ >> CentOS mailing list >> CentOS(a)centos.org >> https://lists.centos.org/mailman/listinfo/centos > > -- > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Pat Haley Email: phaley(a)mit.edu > Center for Ocean Engineering Phone: (617) 253-6824 > Dept. of Mechanical Engineering Fax: (617) 253-8125 > MIT, Room 5-213 http://web.mit.edu/phaley/www/ > 77 Massachusetts Avenue > Cambridge, MA 02139-4301 > > > > ------------------------------ > > Message: 11 > Date: Thu, 01 Sep 2016 03:38:11 +0000 > From: Chris Murphy <lists(a)colorremedies.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] group write permissions not being respected > Message-ID: > <CAJCQCtTfr6rvPGH7uMNzYE9-Q+BfZ784a5n=4S5NekA7O8VxAA(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Try booting with enforcing=0 and if that fixes it, you need to find out > what security label is needed for gluster. > > Chances are it's easiest to use -o context= mount option on the brick, but > if the brick is not exclusive to gluster you'll need chcon -R. > > If that's not it, maybe try the gluster client instead of using NFS. See if > you get a different result that narrows down what's going on. > > My vague recollection is for Samba, without the correct SELinux label, I > could neither read nor write. > > > Chris Murphy > > > ------------------------------ > > Message: 12 > Date: Thu, 1 Sep 2016 11:03:30 +0530 > From: Sidharth Sharma <sharma.sidharth86(a)gmail.com> > To: centos(a)centos.org > Subject: [CentOS] Perl Unsafe Module Path Handling Directory Traversal > Vulnerability ( CVE-2016-1238) > Message-ID: > <CAAQ4EFk7qgWvq=ZtSOugxsgQ1S54y8cFbiG33POQme8+cDrcSw(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Hello Experts, > > When we can expect Security Update for Perl Vulnerability CVE-2016-1238 on > CentOS 6.8 and 7.2? > > -- > With Thanks & Regards: > Sidharth Sharma > > > ------------------------------ > > Message: 13 > Date: Thu, 1 Sep 2016 11:05:36 +0530 > From: Sidharth Sharma <sharma.sidharth86(a)gmail.com> > To: centos(a)centos.org > Subject: [CentOS] Bind Vulnerability CVE-2016-2775 > Message-ID: > <CAAQ4EF=2AeThtVjJitR3JHGhuunRJ4AZHiYDcrp4vcKFxUV=UQ(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Hello Experts, > > When we can expect Security Update for Bind Vulnerability on Centos 6.8/7.2? > ISC BIND Lightweight Resolver Protocol Req Processing Dos Vulnerability: > CVE-2016-2775 > > -- > With Thanks & Regards: > Sidharth Sharma > > > ------------------------------ > > Message: 14 > Date: Thu, 1 Sep 2016 10:26:34 +0200 > From: Toralf Lund <toralf.lund(a)pgs.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] "Windows" share issue; access via smb:// fails, > "mount -t cifs" works > Message-ID: <2265d62b-32b6-6d51-5848-df84f5800723(a)pgs.com> > Content-Type: text/plain; charset="utf-8"; format=flowed > > On 30/08/16 10:00, Toralf Lund wrote: >> Hi, >> >> Is anyone here using smb:// URLs to access "Windows" shares? I've been >> doing this for a while with common file systems at work, and it used >> to work just fine. Then I while back, I started getting issues; I will >> now just keep getting asked for a password when I try to access >> something through smb://. I thought at first that this meant there had >> been some kind of change related to permissions on the shares, but now >> I find that I can mount them just fine using "mount -t cifs". > I found out a bit more about this - I believe that I have the issue > described here: > > http://community.netapp.com/t5/Network-Storage-Protocols-Discussions/samba-… > > In other words, the problem is that "SPNEGO" fails. If I add "client use > spnego = no" to /etc/samba/smb.conf, smbclient access works (I found > that I also got a problem there), but unfortunately, gvfs-mount still > doesn't. The debug output that I get if I run gvfsd on the command line > with "GVFS_DEBUG=1" and "GVFS_SMB_DEBUG=99" actually still report SPNEGO > errors, so it would appear that the smp.conf option is for some reason > ignored. In other words the question may be: > > How do I disabled SPNEGO for gvfs-mount? > > Also, the above suggest that whether this problem occurs depends on > whether "you have SMB signing turned on or not under the 'cifs' options > section", but it not clear to me what options exactly this refers to. > Anyone? > > Oh, and some other posts I found seem to indicate that mount.cifs > doesn't support SPNEGO yet, so I guess that's why a "normal" mount works. > > - Toralf > > >> >> In other words, I get: >> >> gvfs-mount smb://mydomain\;toralf.lund@theserver/myshare >> Password required for share myshare on theserver >> Password: >> Password required for share myshare on theserver >> Password: >> Password required for share myshare on theserver >> Password: >> >> [ I enter the correct password, but gvs-mount keeps asking... >> Behaviour is the same if I try to open the URL in the file manager >> instead. ] >> >> mount -t cifs -o user=toralf.lund,workgroup=mydomain >> //theserver/myshare /tmp_mnt/ >> Password: >> >> [ At this stage the filesystem is mounted, as long as I enter the >> correct password. ] >> >> Does anyone have any idea what is going on here? Why does the VFS >> mount fail when mount.cifs works on the same share? Is there a >> difference in the way authentication works, or something? Has there >> been a change to the smb support that might explain this? >> >> This is on a CentOS 6 x86_64 installation with all updates applied. >> >> - Toralf >> > > > > ------------------------------ > > Message: 15 > Date: Thu, 1 Sep 2016 08:34:08 +0000 > From: James Pearson <james-p(a)moving-picture.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] Bind Vulnerability CVE-2016-2775 > Message-ID: > <85C0B54E4752CA4F873E7C78CF0B26F5010FB3748D(a)LNDWSMBX01.ad.mpc.local> > Content-Type: text/plain; charset="us-ascii" > > Sidharth Sharma: >> >> When we can expect Security Update for Bind Vulnerability on Centos 6.8/7.2? >> ISC BIND Lightweight Resolver Protocol Req Processing Dos Vulnerability: > >CVE-2016-2775 > > See: > > https://access.redhat.com/security/cve/cve-2016-2775 > > James Pearson > > ------------------------------ > > Message: 16 > Date: Thu, 01 Sep 2016 07:45:04 -0400 > From: Mike Burger <mburger(a)bubbanfriends.org> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] Bind Vulnerability CVE-2016-2775 > Message-ID: <400e82588e4172b96a928e1e3aeef9e3(a)bubbanfriends.org> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > On 2016-09-01 4:34 am, James Pearson wrote: >> Sidharth Sharma: >>> >>> When we can expect Security Update for Bind Vulnerability on Centos >>> 6.8/7.2? >>> ISC BIND Lightweight Resolver Protocol Req Processing Dos >>> Vulnerability: >> >CVE-2016-2775 >> >> See: >> >> https://access.redhat.com/security/cve/cve-2016-2775 > > Ouch! > > Affected Packages State > Platform Package State > Red Hat Enterprise Linux 5 bind97 Will not fix > Red Hat Enterprise Linux 6 bind Will not fix > Red Hat Enterprise Linux 5 bind Will not fix > Red Hat Enterprise Linux 7 bind Will not fix > > -- > Mike Burger > http://www.bubbanfriends.org > > "It's always suicide-mission this, save-the-planet that. No one ever > just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1 > > > ------------------------------ > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos > > > End of CentOS Digest, Vol 140, Issue 1 > **************************************

1 0

Re: [CentOS] group write permissions not being respected
by Chris Murphy 02 Sep '16

02 Sep '16

On Thu, Sep 1, 2016, 8:11 AM Pat Haley <phaley(a)mit.edu> wrote: > > For the enforcing=0, is that referring to SELinux? If so, we are not > running SELinux. > OK so neither that nor chcon nor context mount option apply. It's something else. > > On 08/31/2016 11:38 PM, Chris Murphy wrote: > > ---------------------------------------------------------------------------------------- > > Try booting with enforcing=0 and if that fixes it, you need to find out > > what security label is needed for gluster. > > ---------------------------------------------------------------------------------------- > For the enforcing=0, is that referring to SELinux? If so, we are not > running SELinux. > > ----------------------------------------------------------------------------------------- > > > Chances are it's easiest to use -o context= mount option on the brick, > but > > if the brick is not exclusive to gluster you'll need chcon -R. > > ----------------------------------------------------------------------------------------- > We aren't sure exactly what you mean by this second paragraph, can > you expand on this? Are these two exclusive options exclusive? We aren't > sure what you what you mean by "exclusive to gluster" > > ----------------------------------------------------------------------------------------- > > If that's not it, maybe try the gluster client instead of using NFS. See > if > > you get a different result that narrows down what's going on. > > > > My vague recollection is for Samba, without the correct SELinux label, I > > could neither read nor write. > > > > > > Chris Murphy > > _______________________________________________ > > CentOS mailing list > > CentOS(a)centos.org > > https://lists.centos.org/mailman/listinfo/centos > > -- > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Pat Haley Email: phaley(a)mit.edu > Center for Ocean Engineering Phone: (617) 253-6824 > Dept. of Mechanical Engineering Fax: (617) 253-8125 > MIT, Room 5-213 http://web.mit.edu/phaley/www/ > 77 Massachusetts Avenue > Cambridge, MA 02139-4301 > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos >

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss September 2016