From matthias at leopold.priv.at Wed May 4 10:09:57 2016 From: matthias at leopold.priv.at (Matthias Leopold) Date: Wed, 4 May 2016 12:09:57 +0200 Subject: [scl.org] rh-php56-php Version for CentOS Message-ID: <5729CA75.1090102@leopold.priv.at> Hi, is there a reason why the rh-php56-php RPMS for CentOS don't get updated? CentOS has version 5.6.5-7 RHEL has 5.6.5-8 for quite some time thx matthias From hhorak at redhat.com Thu May 5 09:25:21 2016 From: hhorak at redhat.com (Honza Horak) Date: Thu, 5 May 2016 11:25:21 +0200 Subject: [scl.org] rh-php56-php Version for CentOS In-Reply-To: <5729CA75.1090102@leopold.priv.at> References: <5729CA75.1090102@leopold.priv.at> Message-ID: <572B1181.5080705@redhat.com> Rebuild is not automatic and it is best-effort, but it should be done soon. Thanks for pointing to that. Honza On 05/04/2016 12:09 PM, Matthias Leopold wrote: > Hi, > > is there a reason why the rh-php56-php RPMS for CentOS don't get updated? > > CentOS has version 5.6.5-7 > RHEL has 5.6.5-8 for quite some time > > thx > matthias > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg From mark at edwardsmark.com Mon May 9 17:46:56 2016 From: mark at edwardsmark.com (Mark Edwards) Date: Mon, 9 May 2016 10:46:56 -0700 Subject: [scl.org] php7 support? Message-ID: hello - is there a forum to ask simple questions like this? i am wondering about php support. note: you suggested stack-overflow as a forum, but in stack-overflow, if your questions are deemed to be stupid, you get down-voted. Thank you, Mark Edwards -------------- next part -------------- An HTML attachment was scrubbed... URL: From Souvignier at itc.rwth-aachen.de Tue May 10 10:56:38 2016 From: Souvignier at itc.rwth-aachen.de (Souvignier, Daniel) Date: Tue, 10 May 2016 10:56:38 +0000 Subject: [scl.org] php7 support? In-Reply-To: References: Message-ID: <9bb227031b5240178143ee3364688b70@rwthex-w2-a.rwth-ad.de> Hi, there is an scl for php7 in remi repo, see this: http://blog.remirepo.net/post/2015/03/25/PHP-7.0-as-Software-Collection Regards, Daniel Von: sclorg-bounces at redhat.com [mailto:sclorg-bounces at redhat.com] Im Auftrag von Mark Edwards Gesendet: Montag, 9. Mai 2016 19:47 An: sclorg at redhat.com Betreff: [scl.org] php7 support? hello - is there a forum to ask simple questions like this? i am wondering about php support. note: you suggested stack-overflow as a forum, but in stack-overflow, if your questions are deemed to be stupid, you get down-voted. Thank you, Mark Edwards -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5800 bytes Desc: not available URL: From Souvignier at itc.rwth-aachen.de Wed May 11 08:42:59 2016 From: Souvignier at itc.rwth-aachen.de (Souvignier, Daniel) Date: Wed, 11 May 2016 08:42:59 +0000 Subject: [scl.org] php7 support? Message-ID: Hi, again, for php-imap you'll have to use php56-more from www.softwarecollections.org . It's not available in rh-php56. Regards, Daniel -- Daniel Souvignier IT Center Gruppe: Anwendungsbetrieb Abteilung: Systeme und Betrieb RWTH Aachen University Seffenter Weg 23 52074 Aachen Tel.: +49 241 80-29267 souvignier at itc.rwth-aachen.de www.itc.rwth-aachen.de -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5800 bytes Desc: not available URL: From hhorak at redhat.com Wed May 11 10:05:24 2016 From: hhorak at redhat.com (Honza Horak) Date: Wed, 11 May 2016 12:05:24 +0200 Subject: [scl.org] Looking for a new timeslot for SCLo SIG meeting In-Reply-To: <572210DE.4060008@gmail.com> References: <572210DE.4060008@gmail.com> Message-ID: <573303E4.3000901@redhat.com> There were few matches, because not many people have responded, so let me pick one time-slot: Tuesday 13:00 UTC/GMT, 15:00 CEST, 9:00 EDT Let's meet every EVEN week (first time the next week). I'll update the meeting time on https://www.centos.org/community/calendar/ and the wiki. Honza On 04/28/2016 03:32 PM, Honza Horak wrote: > I know about several people who are not very happy about current > timeslot for SCLo SIG sync-up meeting, including me, so.. For everybody > who thinks about attending SCLo SIG meetings regularly in the future, > please, vote which timeslot would be fine for you: > > http://whenisgood.net/5k554ep > > The voting is opened till next Wednesday, 4th May, 23:59 UTC. > > Honza > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg From dominic at cleal.org Mon May 16 15:05:55 2016 From: dominic at cleal.org (Dominic Cleal) Date: Mon, 16 May 2016 16:05:55 +0100 Subject: [scl.org] #0010838: support for RHEL's 7Server in centos-release-scl Message-ID: <5739E1D3.40900@cleal.org> I'm trying to get ticket #0010838 fixed[1] which would allow centos-release-scl (and -rh) to be used unaltered on RHEL to access the SCLo SIG's repositories. Not all RHELs have the upstream RHSCL repos, and there are additional collections published by the SIG that are useful. In the Foreman project I'd like to mirror this RPM to provide centos-release-scl for all EL users during installation to get access to SCLo builds and rebuilds. I'm aware of the RHEL centos-release-sclo builds in Copr[2], but they remove centos-release-rh and I'm trying to ensure the same RPMs can be used on all EL builds. The baseurl in the package is http://mirror.centos.org/centos/$releasever/sclo/$basearch/sclo/, which on RHEL Server expands to .../centos/7Server/sclo/. Only the "7" directory exists on the mirror. Either the mirror could contain symlinks for 7Server -> 7, or the release repo file[3] could be built with the URL hardcoded without using $releasever, which was suggested in today's CBS IRC meeting. Does anybody have any strong preference? If not, I'd like to suggest we change the release repo file. [1]https://bugs.centos.org/view.php?id=10838 [2]https://github.com/sclorg/centos-release-scl#readme [3]https://github.com/alphacc/centos-release-sclo/blob/master/CentOS-SCLo.repo -- Dominic Cleal dominic at cleal.org From hhorak at redhat.com Mon May 16 22:17:13 2016 From: hhorak at redhat.com (Honza Horak) Date: Tue, 17 May 2016 00:17:13 +0200 Subject: [scl.org] CentOS SCLo SIG sync-up meeting (2016-05-17) Message-ID: <573A46E9.20104@redhat.com> The meeting will be at 13:00 UTC (9:00 EST, 15:00 Brno) in #centos-devel on Freenode. Agenda: * setting up Jenkins for Github PRs * anything else? Honza From dominic at cleal.org Tue May 17 08:47:11 2016 From: dominic at cleal.org (Dominic Cleal) Date: Tue, 17 May 2016 09:47:11 +0100 Subject: [scl.org] [CentOS-devel] CentOS SCLo SIG sync-up meeting (2016-05-17) In-Reply-To: <573A46E9.20104@redhat.com> References: <573A46E9.20104@redhat.com> Message-ID: <573ADA8F.8080206@cleal.org> On 16/05/16 23:17, Honza Horak wrote: > The meeting will be at 13:00 UTC (9:00 EST, 15:00 Brno) in #centos-devel > on Freenode. > > Agenda: > * setting up Jenkins for Github PRs > * anything else? * add vagrant-openstack-provider plugin to sclo-vagrant1 for use with the CentOS CI OpenStack instance (I've worked on this at https://copr.fedorainfracloud.org/coprs/domcleal/sclo-vagrant1-openstack/) -- Dominic Cleal dominic at cleal.org From Souvignier at itc.rwth-aachen.de Tue May 17 11:56:52 2016 From: Souvignier at itc.rwth-aachen.de (Souvignier, Daniel) Date: Tue, 17 May 2016 11:56:52 +0000 Subject: [scl.org] [CentOS-devel] CentOS SCLo SIG sync-up meeting (2016-05-17) In-Reply-To: <573ADA8F.8080206@cleal.org> References: <573A46E9.20104@redhat.com> <573ADA8F.8080206@cleal.org> Message-ID: <8fa95eef323441d28960371601f30652@rwthex-w2-a.rwth-ad.de> Hi, what about automating updates of php scls? Also, adding some of the packages available in php5x-more to the official php scls, like the mcrypt and imap modules for example? Regards, Daniel -----Urspr?ngliche Nachricht----- Von: sclorg-bounces at redhat.com [mailto:sclorg-bounces at redhat.com] Im Auftrag von Dominic Cleal Gesendet: Dienstag, 17. Mai 2016 10:47 An: The CentOS developers mailing list. ; sclorg at redhat.com Betreff: Re: [scl.org] [CentOS-devel] CentOS SCLo SIG sync-up meeting (2016-05-17) On 16/05/16 23:17, Honza Horak wrote: > The meeting will be at 13:00 UTC (9:00 EST, 15:00 Brno) in > #centos-devel on Freenode. > > Agenda: > * setting up Jenkins for Github PRs > * anything else? * add vagrant-openstack-provider plugin to sclo-vagrant1 for use with the CentOS CI OpenStack instance (I've worked on this at https://copr.fedorainfracloud.org/coprs/domcleal/sclo-vagrant1-openstack/) -- Dominic Cleal dominic at cleal.org _______________________________________________ SCLorg mailing list SCLorg at redhat.com https://www.redhat.com/mailman/listinfo/sclorg -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5800 bytes Desc: not available URL: From rcollet at redhat.com Tue May 17 12:57:57 2016 From: rcollet at redhat.com (Remi Collet) Date: Tue, 17 May 2016 14:57:57 +0200 Subject: [scl.org] [CentOS-devel] CentOS SCLo SIG sync-up meeting (2016-05-17) In-Reply-To: <8fa95eef323441d28960371601f30652@rwthex-w2-a.rwth-ad.de> References: <573A46E9.20104@redhat.com> <573ADA8F.8080206@cleal.org> <8fa95eef323441d28960371601f30652@rwthex-w2-a.rwth-ad.de> Message-ID: <351c8bc5-fa1d-5cf1-8d28-b261bc89b72d@redhat.com> > Also, adding some of the packages > available in php5x-more to the official php scls, like the mcrypt and > imap modules for example? I have started adding some in centos-sclo-sclo repository See: http://ftp-stud.fht-esslingen.de/pub/Mirrors/centos/7/sclo/x86_64/sclo/sclo-php56/ I was mostly waiting for user feedback before adding more. BTW - mcrypt => missing libmcrypt which is not in RHEL/CentOS for very good reason. See: http://blog.remirepo.net/post/2015/07/07/About-libmcrypt-and-php-mcrypt I think all serious project have dropped dep. on this extension (and often only keep it as a fallback when openssl not availalble) - imap => missing libc-client So all is about, what should we do for dependencies not in base repository (but in EPEL). Remi; -- rcollet at redhat.com | Senior Software Engineer / BaseOS / WebStack team GPG Key: 0x29F16A18 Fingerprint: 5A0E 6F54 D94D 5732 69EE E3FF 614A 6905 29F1 6A18 From hhorak at redhat.com Tue May 17 14:08:07 2016 From: hhorak at redhat.com (Honza Horak) Date: Tue, 17 May 2016 16:08:07 +0200 Subject: [scl.org] [CentOS-devel] CentOS SCLo SIG sync-up meeting (2016-05-17) In-Reply-To: <351c8bc5-fa1d-5cf1-8d28-b261bc89b72d@redhat.com> References: <573A46E9.20104@redhat.com> <573ADA8F.8080206@cleal.org> <8fa95eef323441d28960371601f30652@rwthex-w2-a.rwth-ad.de> <351c8bc5-fa1d-5cf1-8d28-b261bc89b72d@redhat.com> Message-ID: <573B25C7.6060107@redhat.com> On 05/17/2016 02:57 PM, Remi Collet wrote: > >> Also, adding some of the packages >> available in php5x-more to the official php scls, like the mcrypt and >> imap modules for example? > > I have started adding some in centos-sclo-sclo repository > > See: > http://ftp-stud.fht-esslingen.de/pub/Mirrors/centos/7/sclo/x86_64/sclo/sclo-php56/ > > I was mostly waiting for user feedback before adding more. > > BTW > > - mcrypt => missing libmcrypt which is not in RHEL/CentOS for very good > reason. > > See: http://blog.remirepo.net/post/2015/07/07/About-libmcrypt-and-php-mcrypt > > I think all serious project have dropped dep. on this extension (and > often only keep it as a fallback when openssl not availalble) > > - imap => missing libc-client > > > So all is about, what should we do for dependencies not in base > repository (but in EPEL). From my PoV it would be fine to use EPEL deps for packages in SCLo (especially those that do not have a counterpart in RHSCL), but I'm almost sure kbsingh and bstinson will be against -- am I right? Is it a rule to use only packages built in CBS as deps> Honza From kbsingh at redhat.com Tue May 17 14:14:53 2016 From: kbsingh at redhat.com (Karanbir Singh) Date: Tue, 17 May 2016 15:14:53 +0100 Subject: [scl.org] [CentOS-devel] CentOS SCLo SIG sync-up meeting (2016-05-17) In-Reply-To: <573B25C7.6060107@redhat.com> References: <573A46E9.20104@redhat.com> <573ADA8F.8080206@cleal.org> <8fa95eef323441d28960371601f30652@rwthex-w2-a.rwth-ad.de> <351c8bc5-fa1d-5cf1-8d28-b261bc89b72d@redhat.com> <573B25C7.6060107@redhat.com> Message-ID: <540c29e1-4e72-af73-5be2-c8282e17d9d5@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 17/05/16 15:08, Honza Horak wrote: > On 05/17/2016 02:57 PM, Remi Collet wrote: >> >>> Also, adding some of the packages available in php5x-more to >>> the official php scls, like the mcrypt and imap modules for >>> example? >> >> I have started adding some in centos-sclo-sclo repository >> >> See: >> http://ftp-stud.fht-esslingen.de/pub/Mirrors/centos/7/sclo/x86_64/scl o/sclo-php56/ >> >> >> >> I was mostly waiting for user feedback before adding more. >> >> BTW >> >> - mcrypt => missing libmcrypt which is not in RHEL/CentOS for >> very good reason. >> >> See: >> http://blog.remirepo.net/post/2015/07/07/About-libmcrypt-and-php-mcry pt >> >> >> I think all serious project have dropped dep. on this extension (and >> often only keep it as a fallback when openssl not availalble) >> >> - imap => missing libc-client >> >> >> So all is about, what should we do for dependencies not in base >> repository (but in EPEL). > > From my PoV it would be fine to use EPEL deps for packages in SCLo > (especially those that do not have a counterpart in RHSCL), but > I'm almost sure kbsingh and bstinson will be against -- am I right? > Is it a rule to use only packages built in CBS as deps> > > Honza yeah, cant use deps from outside of cbs. you'd need to rebuild those deps from epel. - - KB - -- Karanbir Singh, Project Lead, The CentOS Project, London, UK Red Hat Ext. 8274455 | DID: 0044 207 009 4455 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJXOyddAAoJEI3Oi2Mx7xbtzVAH/R92UH3D5FHLpQUcLZO/nP4T 79o2UBwCLDTf4Aq2EYgUh+QB+VPi/SffJqSrlj5I/WUxGRZ3sB4ks22srR+JmjN4 RKile+awIOillcYOxcekJuW2TmfU+FDhPA2PTz7WcX03+44bjh+i5Lmn8K9aEUcj Ttu/h34rxGz9onjsrB1lkPUSoM925VPB3I18/Qdpbbb6YIet6Q7Dl0lKCOV4n/Dg 97Hl94BDf5qjBXnGhErvyV3iHzlPKnvxRsPClONuj8Oq/qQh8ZzgHV46s0XB30aJ jvIHdCaDSMKkH7Vca5FmOAZZPedTmj7NOVmJ0qWKS9qC730DoBSnV5m5I1cbtsU= =b9Na -----END PGP SIGNATURE----- From hhorak at redhat.com Tue May 17 14:34:04 2016 From: hhorak at redhat.com (Honza Horak) Date: Tue, 17 May 2016 16:34:04 +0200 Subject: [scl.org] [CentOS-devel] CentOS SCLo SIG sync-up meeting (2016-05-17) In-Reply-To: <540c29e1-4e72-af73-5be2-c8282e17d9d5@redhat.com> References: <573A46E9.20104@redhat.com> <573ADA8F.8080206@cleal.org> <8fa95eef323441d28960371601f30652@rwthex-w2-a.rwth-ad.de> <351c8bc5-fa1d-5cf1-8d28-b261bc89b72d@redhat.com> <573B25C7.6060107@redhat.com> <540c29e1-4e72-af73-5be2-c8282e17d9d5@redhat.com> Message-ID: <573B2BDC.2080201@redhat.com> On 05/17/2016 04:14 PM, Karanbir Singh wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 17/05/16 15:08, Honza Horak wrote: >> On 05/17/2016 02:57 PM, Remi Collet wrote: >>> > I think all serious project have dropped dep. on this extension (and >>> often only keep it as a fallback when openssl not availalble) >>> >>> - imap => missing libc-client >>> >>> >>> So all is about, what should we do for dependencies not in base >>> repository (but in EPEL). >> >> From my PoV it would be fine to use EPEL deps for packages in SCLo >> (especially those that do not have a counterpart in RHSCL), but >> I'm almost sure kbsingh and bstinson will be against -- am I right? >> Is it a rule to use only packages built in CBS as deps> >> >> Honza > > > yeah, cant use deps from outside of cbs. you'd need to rebuild those > deps from epel. Do you have some estimation of how many packages would have to be needed? Honza From dominic at cleal.org Tue May 17 15:21:19 2016 From: dominic at cleal.org (Dominic Cleal) Date: Tue, 17 May 2016 16:21:19 +0100 Subject: [scl.org] sclo-vagrant1 1.8.1 builds Message-ID: <573B36EF.7000206@cleal.org> A new sclo-vagrant1-vagrant build appeared today, sclo-vagrant1-vagrant-1.8.1-4.el7, but it doesn't seem to be working well with plugins built with 1.7.4-3.el7 as the root Vagrant installation path changed. It looks like %{vagrant_dir} has expanded differently, causing the root of the Vagrant installation to be at /opt/rh/sclo-vagrant1/root/usr/share/sclo-vagrant1-vagrant/ rather than /opt/rh/sclo-vagrant1/root/usr/share/vagrant/. 1.7.4-3.el7: http://cbs.centos.org/koji/rpminfo?rpmID=23881 1.8.1-4.el7: http://cbs.centos.org/koji/rpminfo?rpmID=56779 The file /usr/lib/rpm/macros.d/macros.vagrant.sclo-vagrant1 in the older build contains "%vagrant_dir %{_datadir}/vagrant", but the newer build uses %{name} which expands to the SCLed name. This breaks builds of vagrant-libvirt which have scriptlets built using %vagrant_plugin_register pointing to ../usr/share/vagrant, and new builds of plugins (http://cbs.centos.org/koji/buildinfo?buildID=11111) are being built with plugin names in the same place, e.g. usr/share/sclo-vagrant1-vagrant-openstack-provider/lib. thrcka, it looks like your build, could you look at this please? Separately I've requested that sclo-vagrant1 be added to the sclo testing repo via https://bugs.centos.org/view.php?id=10869 so I could test the OpenStack package, but we should use the testing repo and process once it's available to check updates work. Also one final point, I couldn't find the source for the update in https://github.com/sclorg-distgit/vagrant/tree/sig-sclo7-sclo-vagrant1-sclo - could the changes be pushed there? Cheers, -- Dominic Cleal dominic at cleal.org From thrcka at redhat.com Tue May 17 16:27:30 2016 From: thrcka at redhat.com (Tomas Hrcka) Date: Tue, 17 May 2016 18:27:30 +0200 Subject: [scl.org] sclo-vagrant1 1.8.1 builds In-Reply-To: <573B36EF.7000206@cleal.org> References: <573B36EF.7000206@cleal.org> Message-ID: <573B4672.2090904@redhat.com> On 05/17/2016 05:21 PM, Dominic Cleal wrote: > A new sclo-vagrant1-vagrant build appeared today, > sclo-vagrant1-vagrant-1.8.1-4.el7, but it doesn't seem to be working > well with plugins built with 1.7.4-3.el7 as the root Vagrant > installation path changed. Sorry for the inconvenience, this has to slip through my hands. > > It looks like %{vagrant_dir} has expanded differently, causing the root > of the Vagrant installation to be at > /opt/rh/sclo-vagrant1/root/usr/share/sclo-vagrant1-vagrant/ rather than > /opt/rh/sclo-vagrant1/root/usr/share/vagrant/. > > 1.7.4-3.el7: http://cbs.centos.org/koji/rpminfo?rpmID=23881 > 1.8.1-4.el7: http://cbs.centos.org/koji/rpminfo?rpmID=56779 > > The file /usr/lib/rpm/macros.d/macros.vagrant.sclo-vagrant1 in the older > build contains "%vagrant_dir %{_datadir}/vagrant", but the newer build > uses %{name} which expands to the SCLed name. I have fixed it back to pkg_name > > This breaks builds of vagrant-libvirt which have scriptlets built using > %vagrant_plugin_register pointing to ../usr/share/vagrant, and new > builds of plugins (http://cbs.centos.org/koji/buildinfo?buildID=11111) > are being built with plugin names in the same place, e.g. > usr/share/sclo-vagrant1-vagrant-openstack-provider/lib. > > thrcka, it looks like your build, could you look at this please? > > Separately I've requested that sclo-vagrant1 be added to the sclo > testing repo via https://bugs.centos.org/view.php?id=10869 so I could > test the OpenStack package, but we should use the testing repo and > process once it's available to check updates work. > > Also one final point, I couldn't find the source for the update in > https://github.com/sclorg-distgit/vagrant/tree/sig-sclo7-sclo-vagrant1-sclo > - could the changes be pushed there? Sorry I have opened pull request instead of pushing there. Changes are now pushed. > > Cheers, > From hhorak at redhat.com Tue May 17 18:34:48 2016 From: hhorak at redhat.com (Honza Horak) Date: Tue, 17 May 2016 20:34:48 +0200 Subject: [scl.org] sclo-vagrant1 1.8.1 builds In-Reply-To: <573B4672.2090904@redhat.com> References: <573B36EF.7000206@cleal.org> <573B4672.2090904@redhat.com> Message-ID: <573B6448.1090509@redhat.com> There is a test that has been running for every new build, but the test itself keeps failing (never worked properly imho). You might want to fix/rewrite it, so you can easily check status of every rebuild: https://github.com/sclorg/sclo-ci-tests/tree/master/collections/sclo-vagrant1-sclo/vagrant-up results are then in https://ci.centos.org/view/SCLo/job/SCLo-sclo-vagrant1-sclo-C7-x86_64/ Honza On 05/17/2016 06:27 PM, Tomas Hrcka wrote: > > > On 05/17/2016 05:21 PM, Dominic Cleal wrote: >> A new sclo-vagrant1-vagrant build appeared today, >> sclo-vagrant1-vagrant-1.8.1-4.el7, but it doesn't seem to be working >> well with plugins built with 1.7.4-3.el7 as the root Vagrant >> installation path changed. > > Sorry for the inconvenience, this has to slip through my hands. > >> >> It looks like %{vagrant_dir} has expanded differently, causing the root >> of the Vagrant installation to be at >> /opt/rh/sclo-vagrant1/root/usr/share/sclo-vagrant1-vagrant/ rather than >> /opt/rh/sclo-vagrant1/root/usr/share/vagrant/. >> >> 1.7.4-3.el7: http://cbs.centos.org/koji/rpminfo?rpmID=23881 >> 1.8.1-4.el7: http://cbs.centos.org/koji/rpminfo?rpmID=56779 >> >> The file /usr/lib/rpm/macros.d/macros.vagrant.sclo-vagrant1 in the older >> build contains "%vagrant_dir %{_datadir}/vagrant", but the newer build >> uses %{name} which expands to the SCLed name. > > I have fixed it back to pkg_name > >> >> This breaks builds of vagrant-libvirt which have scriptlets built using >> %vagrant_plugin_register pointing to ../usr/share/vagrant, and new >> builds of plugins (http://cbs.centos.org/koji/buildinfo?buildID=11111) >> are being built with plugin names in the same place, e.g. >> usr/share/sclo-vagrant1-vagrant-openstack-provider/lib. >> >> thrcka, it looks like your build, could you look at this please? >> >> Separately I've requested that sclo-vagrant1 be added to the sclo >> testing repo via https://bugs.centos.org/view.php?id=10869 so I could >> test the OpenStack package, but we should use the testing repo and >> process once it's available to check updates work. >> >> Also one final point, I couldn't find the source for the update in >> https://github.com/sclorg-distgit/vagrant/tree/sig-sclo7-sclo-vagrant1-sclo >> >> - could the changes be pushed there? > Sorry I have opened pull request instead of pushing there. Changes are > now pushed. >> >> Cheers, >> > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg From dominic at cleal.org Wed May 18 07:33:53 2016 From: dominic at cleal.org (Dominic Cleal) Date: Wed, 18 May 2016 08:33:53 +0100 Subject: [scl.org] sclo-vagrant1 1.8.1 builds In-Reply-To: <573B4672.2090904@redhat.com> References: <573B36EF.7000206@cleal.org> <573B4672.2090904@redhat.com> Message-ID: <573C1AE1.7060103@cleal.org> On 17/05/16 17:27, Tomas Hrcka wrote: > On 05/17/2016 05:21 PM, Dominic Cleal wrote: >> It looks like %{vagrant_dir} has expanded differently, causing the root >> of the Vagrant installation to be at >> /opt/rh/sclo-vagrant1/root/usr/share/sclo-vagrant1-vagrant/ rather than >> /opt/rh/sclo-vagrant1/root/usr/share/vagrant/. >> >> 1.7.4-3.el7: http://cbs.centos.org/koji/rpminfo?rpmID=23881 >> 1.8.1-4.el7: http://cbs.centos.org/koji/rpminfo?rpmID=56779 >> >> The file /usr/lib/rpm/macros.d/macros.vagrant.sclo-vagrant1 in the older >> build contains "%vagrant_dir %{_datadir}/vagrant", but the newer build >> uses %{name} which expands to the SCLed name. > > I have fixed it back to pkg_name Thanks, 1.8.1-5 seems to fix both of these issue. There remains another new one it seems - if you rebuild a plugin against -5, the registration scriptlet runs "/opt/rh/sclo-vagrant1/root/usr/bin/ruby -e". %vagrant_plugin_register now uses %{_bindir}/ruby, but this used to be plain "ruby" - the scl enable should put it in the PATH anyway, so I don't think this is needed. It was changed at https://github.com/sclorg-distgit/vagrant/commit/e448388e0cc88a76d9923d86df3e1615a666eeff#diff-0cc501359f9ff39115559ff49a4f0d47L36. >> Separately I've requested that sclo-vagrant1 be added to the sclo >> testing repo via https://bugs.centos.org/view.php?id=10869 so I could >> test the OpenStack package, but we should use the testing repo and >> process once it's available to check updates work. >> >> Also one final point, I couldn't find the source for the update in >> https://github.com/sclorg-distgit/vagrant/tree/sig-sclo7-sclo-vagrant1-sclo >> - could the changes be pushed there? > Sorry I have opened pull request instead of pushing there. Changes are > now pushed. Ah OK, probably best to push if it's already built. I'll monitor the PRs in that repo in future to help with reviewing. Hopefully the testing repo will help as well so these changes aren't released immediately. -- Dominic Cleal dominic at cleal.org From rcollet at redhat.com Wed May 18 08:25:10 2016 From: rcollet at redhat.com (Remi Collet) Date: Wed, 18 May 2016 10:25:10 +0200 Subject: [scl.org] [CentOS-devel] CentOS SCLo SIG sync-up meeting (2016-05-17) In-Reply-To: <573B2BDC.2080201@redhat.com> References: <573A46E9.20104@redhat.com> <573ADA8F.8080206@cleal.org> <8fa95eef323441d28960371601f30652@rwthex-w2-a.rwth-ad.de> <351c8bc5-fa1d-5cf1-8d28-b261bc89b72d@redhat.com> <573B25C7.6060107@redhat.com> <540c29e1-4e72-af73-5be2-c8282e17d9d5@redhat.com> <573B2BDC.2080201@redhat.com> Message-ID: <591142d2-2708-bc3c-cf3c-ff53a43a08b9@redhat.com> Le 17/05/2016 ? 16:34, Honza Horak a ?crit : >> yeah, cant use deps from outside of cbs. you'd need to rebuild those >> deps from epel. > > Do you have some estimation of how many packages would have to be needed? Few examples: php-imap => libc-client php-mcrypt => libmcrypt php-tidy => libtidy php-mssql => freetds php-interbase => firebird (and probably others) php-pecl-mongodb => libbson + libmongoc php-pecl-amqp => librabbitmq php-pecl-libsodium => libsodium php-pecl-zmq => zeromq ... Remi -- rcollet at redhat.com | Senior Software Engineer / BaseOS / WebStack team GPG Key: 0x29F16A18 Fingerprint: 5A0E 6F54 D94D 5732 69EE E3FF 614A 6905 29F1 6A18 From dominic at cleal.org Wed May 18 15:08:51 2016 From: dominic at cleal.org (Dominic Cleal) Date: Wed, 18 May 2016 16:08:51 +0100 Subject: [scl.org] [CentOS-devel] 'vagrant up' not working after yum update In-Reply-To: <8f9f8477-020a-c8fc-2fc6-7cd9a32a3ccc@redhat.com> References: <8f9f8477-020a-c8fc-2fc6-7cd9a32a3ccc@redhat.com> Message-ID: <573C8583.4070302@cleal.org> On 18/05/16 15:52, Dharmit Shah wrote: > Hello all, > > I'm seeing this behaviour since I did `yum update` today on one of my > CentOS 7 boxes in that, `vagrant up` for libvirt provider throws the error: > > "The provider 'libvirt' could not be found, but was requested to > back the machine 'default'. Please use a provider that exists." > > Details of the issue can be found on [1]. I observed the issue when I > was doing testing for Atomic Developer Bundle (ADB) [2]. Could you try this newer build of sclo-vagrant1-vagrant (the -5 release)? http://cbs.centos.org/koji/buildinfo?buildID=11113 It's been tagged for release already so I expect it'll appear on the mirrors within a few days. (see also https://www.redhat.com/archives/sclorg/2016-May/msg00014.html where this was discussed and hopefully fixed) > Besides that, earlier, one needed to install only two packages - > centos-release-scl and sclo-vagrant1 - to use Vagrant. But now it seems > to have changed and we need to install sclo-vagrant1-vagrant-libvirt as > well as few other packages/dependencies to make it work. I modified my > Ansible playbook [3] which reflects the set of packages I had to add. This appears to have been changed in http://cbs.centos.org/koji/buildinfo?buildID=10807, but I don't see why. The changelog is pretty unhelpful, but comparing the specs shows that %install_scl's been flipped to zero which isn't common in SCL meta RPMs. > What I'm here to understand is that, am I doing something obviously > wrong here to make things work or, did I miss some notification on this > list that had details about the changes? Or is this some kind of > unexpected behaviour? Unexpected to me, I think the RPMs should have been put to the testing repo before being released. -- Dominic Cleal dominic at cleal.org From dmakovey at stanford.edu Wed May 18 16:20:37 2016 From: dmakovey at stanford.edu (Dmitry Makovey) Date: Wed, 18 May 2016 09:20:37 -0700 Subject: [scl.org] Building packages depending on SCL Message-ID: <0fe6d890-4e0e-6714-8db6-d081e7492586@stanford.edu> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, I've been building RPMs for a while, however SCL is a bit "new" to me. I am trying to build an apache module for SCL apache version (httpd24-httpd) . I have located documentation on how to proceed with building SCL package from scratch, however I didn't come across any information on building atop of existing packages, like in my case. Any pointers (URLs etc.) will be deeply appreciated. - -- Sr System and DevOps Engineer SoM IRT -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXPJZOAAoJEHd9jKvw5f8b/FsP/jtopReS0MsW5CvZOEQUxczx 3ku2FQZGdHr7cIZUIXZSkLlqC3AT/oL6Ku01aN8AqiOJrAW+c2bR9+eoL+Tpj9+1 c5n24K/u5Bg0OsdT/1RGPgSicyiWzErVvuLLL8CZED6kMYJ8gxxA1+tKYU7GLHZj taY9E37gI6jyhPFHujqkP7PeqGawIq5o3rYHvpRh+nfioUFlHX6fK6ZNuhjYR2OG panqbaM2EPySXmRgJX8Fho2bkL5tE1Z1yQNa+3RvkienowU32+1f65613cYfwI8T SZ+INvCdu8mVyBaT5L2TXKeAlEt8isl+sUpWKX5nrQdvVR4dQa7m7wYHO6C1KT8f eitzbUQ/e64spUIbnzZVgwx8zXjmhBWh5vCnuCfDNFhyoufL2mvteMQRsMs7QFNq RL5z4iKGgL6mResKfrjVq7mVAjDS8rByqRLl77BBg0X0GoXLm+qsmhQSzheBS1ou GR2tAcVaj92eQWu9MYC9oW+2Fs/ynvaNyP6Z9+tjinRcPBhc+PUQlyH8OStx32of hrNrx/j9QP+Oz7eFWgr9qbQwYqc2SCPWcPhpC73U6movuhI/vCrc/sv0/43Mryw4 VXbHPAs45jnZKJxBkqlgVcUY2Hh+6Smr9LIUbexegOnwNmAYyLu+yMHUtWV7E52j FrsJgXv/N0q+ovQIDWOI =kI6T -----END PGP SIGNATURE----- From rcollet at redhat.com Thu May 19 05:26:45 2016 From: rcollet at redhat.com (Remi Collet) Date: Thu, 19 May 2016 07:26:45 +0200 Subject: [scl.org] Building packages depending on SCL In-Reply-To: <0fe6d890-4e0e-6714-8db6-d081e7492586@stanford.edu> References: <0fe6d890-4e0e-6714-8db6-d081e7492586@stanford.edu> Message-ID: <8a868674-19c9-5442-f594-bfb11e0ba821@redhat.com> Le 18/05/2016 ? 18:20, Dmitry Makovey a ?crit : > > Hi, > > I've been building RPMs for a while, however SCL is a bit "new" to me. > I am trying to build an apache module for SCL apache version > (httpd24-httpd) . I have located documentation on how to proceed with > building SCL package from scratch, however I didn't come across any > information on building atop of existing packages, like in my case. > Any pointers (URLs etc.) will be deeply appreciated. In centos-sclo repository you already have 2 apache modules, you can probably have a look at (diffing with base package in Fedora/EPEL) https://github.com/sclorg-distgit/mod_auth_mellon/tree/sig-sclo7-sclo-httpd24more-sclo https://github.com/sclorg-distgit/mod_ruid2/tree/sig-sclo7-sclo-httpd24more-sclo Hope this helps... Remi > > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > -- rcollet at redhat.com | Senior Software Engineer / BaseOS / WebStack team GPG Key: 0x29F16A18 Fingerprint: 5A0E 6F54 D94D 5732 69EE E3FF 614A 6905 29F1 6A18 From dominic at cleal.org Thu May 19 11:41:02 2016 From: dominic at cleal.org (Dominic Cleal) Date: Thu, 19 May 2016 12:41:02 +0100 Subject: [scl.org] sclo-vagrant1 1.8.1 builds In-Reply-To: <573C1AE1.7060103@cleal.org> References: <573B36EF.7000206@cleal.org> <573B4672.2090904@redhat.com> <573C1AE1.7060103@cleal.org> Message-ID: <573DA64E.90400@cleal.org> On 18/05/16 08:33, Dominic Cleal wrote: > On 17/05/16 17:27, Tomas Hrcka wrote: >> On 05/17/2016 05:21 PM, Dominic Cleal wrote: >>> It looks like %{vagrant_dir} has expanded differently, causing the root >>> of the Vagrant installation to be at >>> /opt/rh/sclo-vagrant1/root/usr/share/sclo-vagrant1-vagrant/ rather than >>> /opt/rh/sclo-vagrant1/root/usr/share/vagrant/. >>> >>> 1.7.4-3.el7: http://cbs.centos.org/koji/rpminfo?rpmID=23881 >>> 1.8.1-4.el7: http://cbs.centos.org/koji/rpminfo?rpmID=56779 >>> >>> The file /usr/lib/rpm/macros.d/macros.vagrant.sclo-vagrant1 in the older >>> build contains "%vagrant_dir %{_datadir}/vagrant", but the newer build >>> uses %{name} which expands to the SCLed name. >> >> I have fixed it back to pkg_name > > Thanks, 1.8.1-5 seems to fix both of these issue. There remains another > new one it seems - if you rebuild a plugin against -5, the registration > scriptlet runs "/opt/rh/sclo-vagrant1/root/usr/bin/ruby -e". > > %vagrant_plugin_register now uses %{_bindir}/ruby, but this used to be > plain "ruby" - the scl enable should put it in the PATH anyway, so I > don't think this is needed. It was changed at > https://github.com/sclorg-distgit/vagrant/commit/e448388e0cc88a76d9923d86df3e1615a666eeff#diff-0cc501359f9ff39115559ff49a4f0d47L36. PR opened at https://github.com/sclorg-distgit/vagrant/pull/2 to revert it. Rebuilding both vagrant and vagrant-openstack-provider against it seems to now produce a working pair of RPMs that install the plugin. -- Dominic Cleal dominic at cleal.org From dmakovey at stanford.edu Thu May 19 15:01:40 2016 From: dmakovey at stanford.edu (Dmitry Makovey) Date: Thu, 19 May 2016 08:01:40 -0700 Subject: [scl.org] Building packages depending on SCL In-Reply-To: <8a868674-19c9-5442-f594-bfb11e0ba821@redhat.com> References: <0fe6d890-4e0e-6714-8db6-d081e7492586@stanford.edu> <8a868674-19c9-5442-f594-bfb11e0ba821@redhat.com> Message-ID: <64ee7562-6c97-08ea-666c-538ced220501@stanford.edu> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 05/18/2016 10:26 PM, Remi Collet wrote: > Le 18/05/2016 ? 18:20, Dmitry Makovey a ?crit : >> >> Hi, >> >> I've been building RPMs for a while, however SCL is a bit "new" >> to me. I am trying to build an apache module for SCL apache >> version (httpd24-httpd) . I have located documentation on how to >> proceed with building SCL package from scratch, however I didn't >> come across any information on building atop of existing >> packages, like in my case. Any pointers (URLs etc.) will be >> deeply appreciated. > > In centos-sclo repository you already have 2 apache modules, you > can probably have a look at (diffing with base package in > Fedora/EPEL) > > https://github.com/sclorg-distgit/mod_auth_mellon/tree/sig-sclo7-sclo- httpd24more-sclo > > > https://github.com/sclorg-distgit/mod_ruid2/tree/sig-sclo7-sclo-httpd2 4more-sclo Thanks > Remi! That is exactly what I needed. This gives me enough info to proceed. > > > Hope this helps... > > Remi > >> >> >> _______________________________________________ SCLorg mailing >> list SCLorg at redhat.com >> https://www.redhat.com/mailman/listinfo/sclorg >> > - -- Sr System and DevOps Engineer SoM IRT -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXPdVUAAoJEHd9jKvw5f8bqhIP/3jadfVQ3wzySPC4RYFm6g4A kBbHhla6Sjq/fgI52Bh0dVXvOzUquBvD9D98uf4S6hO9t7vMK55D4jcJAhrwmzO3 ff16Ahqq+k/9lh9SA7LQgsiiq2D31Ibwpyaf1DYTnEcJcIZGAbfpOIKOK0vHN8qt PmRjKM6p+SFITXGa2DlWzAB/mzGDoX9dV1aDThp5xkkjui+bAmspL0+5USV0zR00 VHVPLIeBnUW48fD+K1cgcH3Piup6hWjR23zk+nrjauP3MId6BGJHjq+EvHYM029Y pdKBrGEZXjR1NeSkWnvsWgnHCj1vY83K/4/cGcVxKzlVbVVezB680gQYSbNOpkg7 WuXJ5lk3WcGQ/2EjYuHNS5Hod8/w2PmDOzyOXMIoyuhC/Yh6m4W4Em+oLqNewZuz A+mmUEwGRSfX3mVdYNMVZaasj2eRQSDbAO4T3joUh1cszGe3eD7uOcb61xQPvY2v lCuEukItKZcNg8jNfSMC0/BmQduXKCwkcave7MhwreObAYJWVLDmHq/t3UZJYY2s M6XBRkejZ0MIwdTN9cApig+8A8qg5OBST+TropFZ09c7s+PlIx4eQ2ylD0hwxQIh q8o1Iy/ovD52GEiW1BFsizNFCKKqZLDM+AjqGRKr3mI64Xw5InsWRA6yxSxH9Wpz l/6JL28hwE2xKX3j1fpm =zJrj -----END PGP SIGNATURE----- From dshah at redhat.com Thu May 19 11:37:54 2016 From: dshah at redhat.com (Dharmit Shah) Date: Thu, 19 May 2016 17:07:54 +0530 Subject: [scl.org] [CentOS-devel] 'vagrant up' not working after yum update In-Reply-To: <573C8583.4070302@cleal.org> References: <8f9f8477-020a-c8fc-2fc6-7cd9a32a3ccc@redhat.com> <573C8583.4070302@cleal.org> Message-ID: On 05/18/2016 08:38 PM, Dominic Cleal wrote: > On 18/05/16 15:52, Dharmit Shah wrote: >> Hello all, >> >> I'm seeing this behaviour since I did `yum update` today on one of my >> CentOS 7 boxes in that, `vagrant up` for libvirt provider throws the error: >> >> "The provider 'libvirt' could not be found, but was requested to >> back the machine 'default'. Please use a provider that exists." >> >> Details of the issue can be found on [1]. I observed the issue when I >> was doing testing for Atomic Developer Bundle (ADB) [2]. > > Could you try this newer build of sclo-vagrant1-vagrant (the -5 > release)? http://cbs.centos.org/koji/buildinfo?buildID=11113 > Yes, it works now. Thanks Dominic! Regards, Dharmit. From dominic at cleal.org Mon May 23 13:51:42 2016 From: dominic at cleal.org (Dominic Cleal) Date: Mon, 23 May 2016 14:51:42 +0100 Subject: [scl.org] centos-release-scl* RPM sources Message-ID: <57430AEE.20201@cleal.org> The centos-release-scl and -rh RPMs shipped in CentOS Extras that point to the SCLo SIG's repos are now stored at this location: https://github.com/sclorg-distgit/centos-release-sclo There's a master branch for EL7 and a separate 'el6' branch as EL6 has some EVR adjustments, so ensure when building that you use the right one. The repo and packages have been maintained by Thomas (alphacc) until now, so thanks to him for moving this to the sclorg organisation. https://wiki.centos.org/SIGGuide/Content/Release contains useful info about the build targets and tags to use in CBS to build release packages to Extras. -- Dominic Cleal dominic at cleal.org From james.hogarth at gmail.com Mon May 23 15:38:51 2016 From: james.hogarth at gmail.com (James Hogarth) Date: Mon, 23 May 2016 16:38:51 +0100 Subject: [scl.org] The SCL wiki page contents and confusing SCL situation Message-ID: Hi, I thought I'd start an article on my personal blog on the various options for newer PHP (in particular), python, ruby etc options in CentOS - particularly given some of the base packages in EL6 have now passed EOL upstream and consequently some applications (eg OwnCloud) now have minimal dependencies greater than in base. What I found on initial looks to SCL was at best confusing and in areas outright misleading, with help needed from Dominic in #centos-devel to work through the present SCL situation. Doing a general Google search (or the @scl keyword in #centos) will take someone to here: https://wiki.centos.org/AdditionalResources/Repositories/SCL This refers to an old centos-release-SCL package which is still in the repos and would direct the user to unmaintained old versions. The correct package is actually centos-release-scl ... yes just the case needs to change. The documentation for centos-release-scl stuff (ie the CentOS SCL SIG stuff) is pretty much nonexistent for a user needing a newer version of a package. These pages are very CentOS developer focused and not really useful for the end user: https://wiki.centos.org/SpecialInterestGroup/SCLo https://wiki.centos.org/SpecialInterestGroup/SCLo/CollectionsList Then once the right package is installed the user can see there is php54, php55 and rh-php56 packages but it's not clear why the difference in the naming and there's nothing that highlights to someone that if they want to use php55 or rh-php56 they'll need to handle a migration to rh-httpd24 as well. I'd suggest the first step is to have centos-release-scl obsolete centos-release-SCL so that users are not left on an unmaintained repository. Then as I gather data for my article I'd really like to flesh out and improve the 'user facing' SCL wiki page. Thoughts on this? James -------------- next part -------------- An HTML attachment was scrubbed... URL: From manuel.vacelet at enalean.com Fri May 27 13:42:42 2016 From: manuel.vacelet at enalean.com (Vacelet, Manuel) Date: Fri, 27 May 2016 15:42:42 +0200 Subject: [scl.org] Weird behavior of httpd24-httpd Message-ID: Hi all, I'm facing an issue that seems specific to httpd24-httpd from scl and I'm having hard time to understand were / how to report the bug properly. Where can I look if my issue is already identified ? How can I report a new one ? Thanks, Manuel (I of course looked at https://bugs.centos.org/view_all_bug_page.php but I don't understand how to identify httpd24-httpd bugs) -------------- next part -------------- An HTML attachment was scrubbed... URL: From hhorak at redhat.com Tue May 31 12:53:52 2016 From: hhorak at redhat.com (Honza Horak) Date: Tue, 31 May 2016 14:53:52 +0200 Subject: [scl.org] Weird behavior of httpd24-httpd In-Reply-To: References: Message-ID: <574D8960.8010009@redhat.com> We don't have any specific component in bugs.centos.org yet, so until we have something there, feel free to use: https://bugzilla.redhat.com/enter_bug.cgi?product=softwarecollections.org Honza On 05/27/2016 03:42 PM, Vacelet, Manuel wrote: > Hi all, > > I'm facing an issue that seems specific to httpd24-httpd from scl and > I'm having hard time to understand were / how to report the bug properly. > > Where can I look if my issue is already identified ? > > How can I report a new one ? > > Thanks, > Manuel > > (I of course looked at https://bugs.centos.org/view_all_bug_page.php but > I don't understand how to identify httpd24-httpd bugs) > > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > From manuel.vacelet at enalean.com Tue May 31 13:54:00 2016 From: manuel.vacelet at enalean.com (Vacelet, Manuel) Date: Tue, 31 May 2016 15:54:00 +0200 Subject: [scl.org] Weird behavior of httpd24-httpd In-Reply-To: <574D8960.8010009@redhat.com> References: <574D8960.8010009@redhat.com> Message-ID: Thanks Honza, For internet archives, here is the link to the weird behavior: https://bugzilla.redhat.com/show_bug.cgi?id=1341233 Manuel On Tue, May 31, 2016 at 2:53 PM, Honza Horak wrote: > We don't have any specific component in bugs.centos.org yet, so until we > have something there, feel free to use: > https://bugzilla.redhat.com/enter_bug.cgi?product=softwarecollections.org > > Honza > > > On 05/27/2016 03:42 PM, Vacelet, Manuel wrote: > >> Hi all, >> >> I'm facing an issue that seems specific to httpd24-httpd from scl and >> I'm having hard time to understand were / how to report the bug properly. >> >> Where can I look if my issue is already identified ? >> >> How can I report a new one ? >> >> Thanks, >> Manuel >> >> (I of course looked at https://bugs.centos.org/view_all_bug_page.php but >> I don't understand how to identify httpd24-httpd bugs) >> >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: