From ncoghlan at redhat.com Mon Apr 3 09:18:09 2017 From: ncoghlan at redhat.com (Nick Coghlan) Date: Mon, 3 Apr 2017 19:18:09 +1000 Subject: [scl.org] Python 3.6 availability In-Reply-To: References: <69bb8b75b19f849c61d7bcf225edd22e@posteo.net> Message-ID: On Fri, Mar 31, 2017 at 7:02 PM, Remi Collet wrote: > Le 31/03/2017 ? 10:30, Nick Coghlan a ?crit : > >> Remi, do you have access to edit the CentOS wiki? It would be good to >> provide a pointer to https://github.com/sclorg-distgit from >> https://wiki.centos.org/SpecialInterestGroup/SCLo > > Please, review if this change seems clear enough : > > https://wiki.centos.org/SpecialInterestGroup/SCLo#head-429ebba9d9c8bcd7e55c1ae23c7ba652901a629c Looks good. The other place that could potentially use an update is this one: ============== Steps for adding a new collection TBD ============== Even if there are plans in place to change the process, would it make sense to at least write down how the current sclo-* packages got started and recommend that others interested in publishing a community collection adopt the same approach? Cheers, Nick. -- Nick Coghlan Red Hat Platform Engineering, Brisbane From hhorak at redhat.com Mon Apr 10 13:33:01 2017 From: hhorak at redhat.com (Honza Horak) Date: Mon, 10 Apr 2017 15:33:01 +0200 Subject: [scl.org] Asking questions via StackOverflow In-Reply-To: References: Message-ID: <1653a0ce-6763-1c30-169f-9a66850ca5e4@redhat.com> Hi, we track this request at https://bugs.centos.org/view.php?id=12844 and just need to find a person eligible (Evolution seems to be the right person) for changing the page. So far I don't see any reason why adding links to keys should be problem.. except it takes time, which I'm sorry about.. :) As for creating the tag, it would be great if you could create one for us, because I don't have enough reputation on StackOverflow.. and not sure anybody else from SCL folks here does.. Honza On 03/23/2017 12:19 PM, Thomas Jones wrote: > The FAQ page says to ask questions on StackOverflow and use the > "software-collections" tag. This tag is not currently available on > StackOverflow and my points-count is too low to create it, myself. Any > chance this lack of tac can be rectified by someone on the SCL team? > > At any rate, the question I was attempting to post to StackOverflow was: > > /Our security folks prefer that we enable GPG-checking for all RPMs to > be installed. We've recently started using packages from the CentOS.Org > packaging of Software Collections. When I try to install these, yum > helpfully yells at me about not having verifiable keys. When I look at > the CentOS.Org site's page concerning GPG keys, the SCL packages are > shown as having a key/fingerprint, but, unlike the other keys listed on > that page, there's no download link./ > > /Is the GPG verification key simply not available or am I simply missing > something blindingly obvious. At any rate, any help in tracking down a > checking-key that I can install to my systems would be of great assistance./ > > > So, in short, is my goal achievable. If so, where do I find the > verification keys and not just the key's printout? > > -- > You can only be -so- accurate with a claw-hammer. --me > > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > From Fedora at FamilleCollet.com Mon Apr 10 13:59:26 2017 From: Fedora at FamilleCollet.com (Remi Collet) Date: Mon, 10 Apr 2017 15:59:26 +0200 Subject: [scl.org] Updated sclo-php* packages available for testing Message-ID: As, new RHSCL 2.4beta is available for testing, and as point release can be used for new features, a set of php extensions have been updated and pushed to testing repository: For rh-php56: * sclo-php56-php-pecl-http-2.6.0-1.el6 * sclo-php56-php-pecl-mongodb-1.2.8-1.el6 For rh-php70: * sclo-php70-php-pecl-http-3.1.0-1.el6 * sclo-php70-php-pecl-mongodb-1.2.8-1.el6 * sclo-php70-php-pecl-xdebug-2.5.1-1.el6 I plan to push to stable only when RHSCL 2.4 will be GA. Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo From dominic at cleal.org Mon Apr 10 13:51:36 2017 From: dominic at cleal.org (Dominic Cleal) Date: Mon, 10 Apr 2017 14:51:36 +0100 Subject: [scl.org] Asking questions via StackOverflow In-Reply-To: <1653a0ce-6763-1c30-169f-9a66850ca5e4@redhat.com> References: <1653a0ce-6763-1c30-169f-9a66850ca5e4@redhat.com> Message-ID: On 10/04/17 14:33, Honza Horak wrote: > As for creating the tag, it would be great if you could create one for > us, because I don't have enough reputation on StackOverflow.. and not > sure anybody else from SCL folks here does.. I've created a tag called "software-collections" on the main Stack Overflow site: http://stackoverflow.com/questions/tagged/software-collections http://stackoverflow.com/tags/software-collections/info The tag wiki text is being reviewed at the moment. Please feel free to edit existing questions and add it. -- Dominic Cleal dominic at cleal.org From hhorak at redhat.com Mon Apr 10 15:00:03 2017 From: hhorak at redhat.com (Honza Horak) Date: Mon, 10 Apr 2017 17:00:03 +0200 Subject: [scl.org] New git package In-Reply-To: References: <0de1d08ab1e04155bd60f5f394161076@rwthex-w2-b.rwth-ad.de> <5d2dcc955f5549d48e13ba4b41e080d9@rwthex-s1-a.rwth-ad.de> <04a85aade986483fbf550ca02a46e57d@rwthex-w2-b.rwth-ad.de> Message-ID: <47a4bb5c-a201-c736-7d05-11ee58907d14@redhat.com> Yes, they do, if there is good enough reason (security or very important fix). We definitely don't include all fixes. Anyway, if there are reasons to have a newer git SCL, I'm totally not against, we can have sclo-git212.. the changes in Fedora SPEC are not that big.. Honza On 03/10/2017 02:03 PM, Souvignier, Daniel wrote: > Thing is: When will git 2.9 itself be EOL? Or do upstream patches get > backported into scls as well (similar to normal packages)? > > Regards, > Daniel > > -- > Daniel Souvignier > > IT Center > Gruppe: Linux-basierte Anwendungen > 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 > > > -----Urspr?ngliche Nachricht----- > Von: Jarek Polok [mailto:Jaroslaw.Polok at cern.ch] > Gesendet: Freitag, 10. M?rz 2017 13:46 > An: Souvignier, Daniel ; sclorg at redhat.com > Betreff: Re: AW: [scl.org] New git package > > > On 03/10/2017 12:56 PM, Souvignier, Daniel wrote: >> That's true, but it's a quite old collection already and I'm not sure >> if it still gets updates, so it would be better to do a new one. I >> know that I can use the old one for now. > > Software Collections 2.3 including git 2.9.3 has been released November > 2016 and its Retirement Date is November 2018. (these are the dates for > upstream Red Hat product) (git 2.9.3 itself is few months older of course) > > So I think its still OK to use it for some time > > Best Regards > > Jarek > > >> >> Regards, >> Daniel >> >> -- >> Daniel Souvignier >> >> IT Center >> Gruppe: Linux-basierte Anwendungen >> 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 >> >> >> -----Urspr?ngliche Nachricht----- >> Von: sclorg-bounces at redhat.com [mailto:sclorg-bounces at redhat.com] Im >> Auftrag von Jarek Polok >> Gesendet: Freitag, 10. M?rz 2017 11:35 >> An: sclorg at redhat.com >> Betreff: Re: [scl.org] New git package >> >> Hello >> >> On 03/10/2017 11:17 AM, Souvignier, Daniel wrote: >>> Forgot to include a link, see here: >>> https://gitlab.com/gitlab-org/gitlab-ce/issues/19609 >>> >> >> Software collections already do provide Git 2.9(.3): >> >> https://www.softwarecollections.org/en/scls/rhscl/rh-git29/ >> >> >> Best Regards >> >> Jarek >> __ >> ------------------------------------------------------- >> _ Jaroslaw_Polok ___________________ CERN - IT/CM/LCS _ _ >> http://cern.ch/~jpolok ________ tel_+41_22_767_1834 _ >> ______________________________________+41_75_411_9487 _ >> >> >> _______________________________________________ >> SCLorg mailing list >> SCLorg at redhat.com >> https://www.redhat.com/mailman/listinfo/sclorg >> > > > -- > __ > ------------------------------------------------------- > _ Jaroslaw_Polok ___________________ CERN - IT/CM/LCS _ _ > http://cern.ch/~jpolok ________ tel_+41_22_767_1834 _ > ______________________________________+41_75_411_9487 _ > > > > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > From hhorak at redhat.com Mon Apr 10 15:01:44 2017 From: hhorak at redhat.com (Honza Horak) Date: Mon, 10 Apr 2017 17:01:44 +0200 Subject: [scl.org] Asking questions via StackOverflow In-Reply-To: References: <1653a0ce-6763-1c30-169f-9a66850ca5e4@redhat.com> Message-ID: <27409c23-350d-0ff6-2dc1-f82a259f1002@redhat.com> Thanks a lot!! Honza On 04/10/2017 03:51 PM, Dominic Cleal wrote: > On 10/04/17 14:33, Honza Horak wrote: >> As for creating the tag, it would be great if you could create one for >> us, because I don't have enough reputation on StackOverflow.. and not >> sure anybody else from SCL folks here does.. > > I've created a tag called "software-collections" on the main Stack > Overflow site: > > http://stackoverflow.com/questions/tagged/software-collections > http://stackoverflow.com/tags/software-collections/info > > The tag wiki text is being reviewed at the moment. > > Please feel free to edit existing questions and add it. > From ncoghlan at redhat.com Tue Apr 11 08:24:39 2017 From: ncoghlan at redhat.com (Nick Coghlan) Date: Tue, 11 Apr 2017 18:24:39 +1000 Subject: [scl.org] Python 3.6 availability In-Reply-To: References: <69bb8b75b19f849c61d7bcf225edd22e@posteo.net> Message-ID: On Fri, Mar 31, 2017 at 6:30 PM, Nick Coghlan wrote: > On Sun, Mar 26, 2017 at 12:50 AM, meson wrote: >> Hi, >> >> is there any estimate on when Python 3.6 will be available as SCL? >> >> Our devs are asking about it. If it's going to take a long time, I'll try my >> hand at building the packages myself. > > It likely makes sense to have some community maintained sclo-* Python > packages I've been mulling this idea over for the past couple of weeks, and I'm wondering if it might make sense to create a rolling "sclo-python3" SCL, that's initially forked from https://www.softwarecollections.org/en/scls/rhscl/rh-python35/, but explicitly promises to rebase to new Python feature releases when they come out. So if people were happy to always run on the leading edge (even for X.Y.0 releases), they could use "sclo-python3", but if they wanted to stay on a particular X.Y release for a while, they would need to switch to the downstream rh-pythonXY SCLs. Remi, if I wanted to do that, where would I start? https://github.com/sclorg-distgit is useful as a reference for submitting changes to existing community SCLs, but it doesn't provide any guidance on how to start a new one (and that info is also missing from the wiki). Cheers, Nick. -- Nick Coghlan Red Hat Platform Engineering, Brisbane From ncoghlan at redhat.com Tue Apr 11 08:42:25 2017 From: ncoghlan at redhat.com (Nick Coghlan) Date: Tue, 11 Apr 2017 18:42:25 +1000 Subject: [scl.org] Asking questions via StackOverflow In-Reply-To: References: <1653a0ce-6763-1c30-169f-9a66850ca5e4@redhat.com> Message-ID: On Mon, Apr 10, 2017 at 11:51 PM, Dominic Cleal wrote: > On 10/04/17 14:33, Honza Horak wrote: >> As for creating the tag, it would be great if you could create one for >> us, because I don't have enough reputation on StackOverflow.. and not >> sure anybody else from SCL folks here does.. > > I've created a tag called "software-collections" on the main Stack > Overflow site: > > http://stackoverflow.com/questions/tagged/software-collections > http://stackoverflow.com/tags/software-collections/info Thanks for that! > The tag wiki text is being reviewed at the moment. The main description has been approved now, the tooltip is just waiting for a 3rd reviewer to give it the thumbs up. Cheers, Nick. -- Nick Coghlan Red Hat Platform Engineering, Brisbane From Jaroslaw.Polok at cern.ch Tue Apr 11 13:08:42 2017 From: Jaroslaw.Polok at cern.ch (Jarek Polok) Date: Tue, 11 Apr 2017 15:08:42 +0200 Subject: [scl.org] New git package In-Reply-To: <47a4bb5c-a201-c736-7d05-11ee58907d14@redhat.com> References: <0de1d08ab1e04155bd60f5f394161076@rwthex-w2-b.rwth-ad.de> <5d2dcc955f5549d48e13ba4b41e080d9@rwthex-s1-a.rwth-ad.de> <04a85aade986483fbf550ca02a46e57d@rwthex-w2-b.rwth-ad.de> <47a4bb5c-a201-c736-7d05-11ee58907d14@redhat.com> Message-ID: <607dc577-d8f0-e1a1-1c50-428d2233f737@cern.ch> On 04/10/2017 05:00 PM, Honza Horak wrote: > Yes, they do, if there is good enough reason (security or very important > fix). We definitely don't include all fixes. > > Anyway, if there are reasons to have a newer git SCL, I'm totally not > against, we can have sclo-git212.. the changes in Fedora SPEC are not > that big.. > OK, let me have a look at this then (since already guilty for one git SCLo .. ;-)) Jarek > Honza > > On 03/10/2017 02:03 PM, Souvignier, Daniel wrote: >> Thing is: When will git 2.9 itself be EOL? Or do upstream patches get >> backported into scls as well (similar to normal packages)? >> >> Regards, >> Daniel >> >> -- >> Daniel Souvignier >> >> IT Center >> Gruppe: Linux-basierte Anwendungen >> 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 >> >> >> -----Urspr?ngliche Nachricht----- >> Von: Jarek Polok [mailto:Jaroslaw.Polok at cern.ch] >> Gesendet: Freitag, 10. M?rz 2017 13:46 >> An: Souvignier, Daniel ; sclorg at redhat.com >> Betreff: Re: AW: [scl.org] New git package >> >> >> On 03/10/2017 12:56 PM, Souvignier, Daniel wrote: >>> That's true, but it's a quite old collection already and I'm not sure >>> if it still gets updates, so it would be better to do a new one. I >>> know that I can use the old one for now. >> >> Software Collections 2.3 including git 2.9.3 has been released November >> 2016 and its Retirement Date is November 2018. (these are the dates for >> upstream Red Hat product) (git 2.9.3 itself is few months older of >> course) >> >> So I think its still OK to use it for some time >> >> Best Regards >> >> Jarek >> >> >>> >>> Regards, >>> Daniel >>> >>> -- >>> Daniel Souvignier >>> >>> IT Center >>> Gruppe: Linux-basierte Anwendungen >>> 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 >>> >>> >>> -----Urspr?ngliche Nachricht----- >>> Von: sclorg-bounces at redhat.com [mailto:sclorg-bounces at redhat.com] Im >>> Auftrag von Jarek Polok >>> Gesendet: Freitag, 10. M?rz 2017 11:35 >>> An: sclorg at redhat.com >>> Betreff: Re: [scl.org] New git package >>> >>> Hello >>> >>> On 03/10/2017 11:17 AM, Souvignier, Daniel wrote: >>>> Forgot to include a link, see here: >>>> https://gitlab.com/gitlab-org/gitlab-ce/issues/19609 >>>> >>> >>> Software collections already do provide Git 2.9(.3): >>> >>> https://www.softwarecollections.org/en/scls/rhscl/rh-git29/ >>> >>> >>> Best Regards >>> >>> Jarek >>> __ >>> ------------------------------------------------------- >>> _ Jaroslaw_Polok ___________________ CERN - IT/CM/LCS _ _ >>> http://cern.ch/~jpolok ________ tel_+41_22_767_1834 _ >>> ______________________________________+41_75_411_9487 _ >>> >>> >>> _______________________________________________ >>> SCLorg mailing list >>> SCLorg at redhat.com >>> https://www.redhat.com/mailman/listinfo/sclorg >>> >> >> >> -- >> __ >> ------------------------------------------------------- >> _ Jaroslaw_Polok ___________________ CERN - IT/CM/LCS _ _ >> http://cern.ch/~jpolok ________ tel_+41_22_767_1834 _ >> ______________________________________+41_75_411_9487 _ >> >> >> >> >> _______________________________________________ >> SCLorg mailing list >> SCLorg at redhat.com >> https://www.redhat.com/mailman/listinfo/sclorg >> > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg -- __ ------------------------------------------------------- _ Jaroslaw_Polok ___________________ CERN - IT/CM/LCS _ _ http://cern.ch/~jpolok ________ tel_+41_22_767_1834 _ ______________________________________+41_75_411_9487 _ From hhorak at redhat.com Thu Apr 13 08:05:00 2017 From: hhorak at redhat.com (Honza Horak) Date: Thu, 13 Apr 2017 10:05:00 +0200 Subject: [scl.org] Python 3.6 availability In-Reply-To: References: <69bb8b75b19f849c61d7bcf225edd22e@posteo.net> Message-ID: <75fa5dfe-d9b6-ee04-cb90-38d9d19e3585@redhat.com> On 04/11/2017 10:24 AM, Nick Coghlan wrote: > On Fri, Mar 31, 2017 at 6:30 PM, Nick Coghlan wrote: >> On Sun, Mar 26, 2017 at 12:50 AM, meson wrote: >>> Hi, >>> >>> is there any estimate on when Python 3.6 will be available as SCL? >>> >>> Our devs are asking about it. If it's going to take a long time, I'll try my >>> hand at building the packages myself. >> >> It likely makes sense to have some community maintained sclo-* Python >> packages > > I've been mulling this idea over for the past couple of weeks, and I'm > wondering if it might make sense to create a rolling "sclo-python3" > SCL, that's initially forked from > https://www.softwarecollections.org/en/scls/rhscl/rh-python35/, but > explicitly promises to rebase to new Python feature releases when they > come out. > > So if people were happy to always run on the leading edge (even for > X.Y.0 releases), they could use "sclo-python3", but if they wanted to > stay on a particular X.Y release for a while, they would need to > switch to the downstream rh-pythonXY SCLs. > > Remi, if I wanted to do that, where would I start? > https://github.com/sclorg-distgit is useful as a reference for > submitting changes to existing community SCLs, but it doesn't provide > any guidance on how to start a new one (and that info is also missing > from the wiki). Hi Nick, I've finally put some short guidance to: https://wiki.centos.org/SpecialInterestGroup/SCLo#head-b408f06ad89fd3a67686f755eafac7ce310ee081 I think that by this mail you basically did the step "Propose adding a new SCL on the mailing list", so now we should agree on the naming and SCL purpose. From my PoV, the last proposal of having "sclo-python3" with "always latest major Python 3" looks good to me, I'll also ask python maint team for their opinion, but if nobody is against here, we can go with this approach. The next step will be you (or the person who is going to build the packages) becoming a SIG member (https://wiki.centos.org/HowTos/CommunityBuildSystem) and then we need to request build tags in the cbs.centos.org (https://wiki.centos.org/SpecialInterestGroup/SCLo#head-4ce81a8b651b8a1217a0c97f757e0eab869bea48). Whether you'll find https://github.com/sclorg-distgit useful for development, or it will be used only for adding sources after build, it's up to you.. Let me know if you have any further questions.. Honza From torsava at redhat.com Thu Apr 13 14:27:19 2017 From: torsava at redhat.com (Tomas Orsava) Date: Thu, 13 Apr 2017 16:27:19 +0200 Subject: [scl.org] Python3 (always latest) community SCL In-Reply-To: References: Message-ID: Hi! On 04/11/2017 10:24 AM, Nick Coghlan wrote: > I've been mulling this idea over for the past couple of weeks, and I'm > wondering if it might make sense to create a rolling "sclo-python3" > SCL, that's initially forked from > https://www.softwarecollections.org/en/scls/rhscl/rh-python35/, but > explicitly promises to rebase to new Python feature releases when they > come out. > > So if people were happy to always run on the leading edge (even for > X.Y.0 releases), they could use "sclo-python3", but if they wanted to > stay on a particular X.Y release for a while, they would need to > switch to the downstream rh-pythonXY SCLs. > > Remi, if I wanted to do that, where would I start? > https://github.com/sclorg-distgit is useful as a reference for > submitting changes to existing community SCLs, but it doesn't provide > any guidance on how to start a new one (and that info is also missing > from the wiki). It would be great to have a state-of-the-art Python in Enterprise Linux, but I think it would be better using the existing (though lacking maintenance) Python 3 in EPEL [0] mechanism. While installing and using SCLs isn't hard, I think an RPM packaged version is still easier for both maintenance and usage and people can have EPEL packages built against it as well. In addition the transition mechanism is smoother, as two Python versions are coexisting during the transition period, whereas the rolling SCL would just switch and everyone would have to immediately adjust. What would be the advantage of creating a rolling 'scl-python3' collection over the EPEL mechanism [1]? [0] https://fedoraproject.org/wiki/User:Bkabrda/EPEL7_Python3 [1] https://admin.fedoraproject.org/pkgdb/package/rpms/python34/ All the best, Tomas From Fedora at FamilleCollet.com Thu Apr 13 16:24:39 2017 From: Fedora at FamilleCollet.com (Remi Collet) Date: Thu, 13 Apr 2017 18:24:39 +0200 Subject: [scl.org] Asking questions via StackOverflow In-Reply-To: References: <1653a0ce-6763-1c30-169f-9a66850ca5e4@redhat.com> Message-ID: Le 10/04/2017 ? 15:51, Dominic Cleal a ?crit : > On 10/04/17 14:33, Honza Horak wrote: >> As for creating the tag, it would be great if you could create one for >> us, because I don't have enough reputation on StackOverflow.. and not >> sure anybody else from SCL folks here does.. > > I've created a tag called "software-collections" on the main Stack > Overflow site: > > http://stackoverflow.com/questions/tagged/software-collections > http://stackoverflow.com/tags/software-collections/info > > The tag wiki text is being reviewed at the moment. > > Please feel free to edit existing questions and add it. > Would it be possible to also create this tag on serverfault ? Ex: https://serverfault.com/questions/844381 Remi. From Fedora at FamilleCollet.com Fri Apr 14 06:36:00 2017 From: Fedora at FamilleCollet.com (Remi Collet) Date: Fri, 14 Apr 2017 08:36:00 +0200 Subject: [scl.org] Asking questions via StackOverflow In-Reply-To: References: <1653a0ce-6763-1c30-169f-9a66850ca5e4@redhat.com> Message-ID: <95a049cf-a187-668c-152f-6ba646b14d78@FamilleCollet.com> Le 13/04/2017 ? 18:24, Remi Collet a ?crit : > Le 10/04/2017 ? 15:51, Dominic Cleal a ?crit : >> On 10/04/17 14:33, Honza Horak wrote: >>> As for creating the tag, it would be great if you could create one for >>> us, because I don't have enough reputation on StackOverflow.. and not >>> sure anybody else from SCL folks here does.. >> >> I've created a tag called "software-collections" on the main Stack >> Overflow site: >> >> http://stackoverflow.com/questions/tagged/software-collections >> http://stackoverflow.com/tags/software-collections/info >> >> The tag wiki text is being reviewed at the moment. >> >> Please feel free to edit existing questions and add it. >> > > Would it be possible to also create this tag on serverfault ? > > Ex: https://serverfault.com/questions/844381 BTW, already exists... https://serverfault.com/questions/tagged/scl > > > > Remi. > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > From Souvignier at itc.rwth-aachen.de Tue Apr 18 06:49:15 2017 From: Souvignier at itc.rwth-aachen.de (Souvignier, Daniel) Date: Tue, 18 Apr 2017 06:49:15 +0000 Subject: [scl.org] New git package In-Reply-To: <47a4bb5c-a201-c736-7d05-11ee58907d14@redhat.com> References: <0de1d08ab1e04155bd60f5f394161076@rwthex-w2-b.rwth-ad.de> <5d2dcc955f5549d48e13ba4b41e080d9@rwthex-s1-a.rwth-ad.de> <04a85aade986483fbf550ca02a46e57d@rwthex-w2-b.rwth-ad.de> <47a4bb5c-a201-c736-7d05-11ee58907d14@redhat.com> Message-ID: <2fc3811046b44c78b2dc5fac54555d17@rwthex-w2-b.rwth-ad.de> Hi Honza, thanks for the info. I just found out that it is not necessary to update the client version of git to work with GitLab, it's just the package that's running on the GitLab server itself that is important. As that one is included in the gitlab omnibus package already, nothing has to be done here. Kind regards, Daniel -- Daniel Souvignier IT Center Gruppe: Linux-basierte Anwendungen 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 -----Urspr?ngliche Nachricht----- Von: sclorg-bounces at redhat.com [mailto:sclorg-bounces at redhat.com] Im Auftrag von Honza Horak Gesendet: Montag, 10. April 2017 17:00 An: sclorg at redhat.com Betreff: Re: [scl.org] New git package Yes, they do, if there is good enough reason (security or very important fix). We definitely don't include all fixes. Anyway, if there are reasons to have a newer git SCL, I'm totally not against, we can have sclo-git212.. the changes in Fedora SPEC are not that big.. Honza On 03/10/2017 02:03 PM, Souvignier, Daniel wrote: > Thing is: When will git 2.9 itself be EOL? Or do upstream patches get > backported into scls as well (similar to normal packages)? > > Regards, > Daniel > > -- > Daniel Souvignier > > IT Center > Gruppe: Linux-basierte Anwendungen > 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 > > > -----Urspr?ngliche Nachricht----- > Von: Jarek Polok [mailto:Jaroslaw.Polok at cern.ch] > Gesendet: Freitag, 10. M?rz 2017 13:46 > An: Souvignier, Daniel ; > sclorg at redhat.com > Betreff: Re: AW: [scl.org] New git package > > > On 03/10/2017 12:56 PM, Souvignier, Daniel wrote: >> That's true, but it's a quite old collection already and I'm not sure >> if it still gets updates, so it would be better to do a new one. I >> know that I can use the old one for now. > > Software Collections 2.3 including git 2.9.3 has been released > November > 2016 and its Retirement Date is November 2018. (these are the dates > for upstream Red Hat product) (git 2.9.3 itself is few months older of > course) > > So I think its still OK to use it for some time > > Best Regards > > Jarek > > >> >> Regards, >> Daniel >> >> -- >> Daniel Souvignier >> >> IT Center >> Gruppe: Linux-basierte Anwendungen >> 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 >> >> >> -----Urspr?ngliche Nachricht----- >> Von: sclorg-bounces at redhat.com [mailto:sclorg-bounces at redhat.com] Im >> Auftrag von Jarek Polok >> Gesendet: Freitag, 10. M?rz 2017 11:35 >> An: sclorg at redhat.com >> Betreff: Re: [scl.org] New git package >> >> Hello >> >> On 03/10/2017 11:17 AM, Souvignier, Daniel wrote: >>> Forgot to include a link, see here: >>> https://gitlab.com/gitlab-org/gitlab-ce/issues/19609 >>> >> >> Software collections already do provide Git 2.9(.3): >> >> https://www.softwarecollections.org/en/scls/rhscl/rh-git29/ >> >> >> Best Regards >> >> Jarek >> __ >> ------------------------------------------------------- >> _ Jaroslaw_Polok ___________________ CERN - IT/CM/LCS _ _ >> http://cern.ch/~jpolok ________ tel_+41_22_767_1834 _ >> ______________________________________+41_75_411_9487 _ >> >> >> _______________________________________________ >> SCLorg mailing list >> SCLorg at redhat.com >> https://www.redhat.com/mailman/listinfo/sclorg >> > > > -- > __ > ------------------------------------------------------- > _ Jaroslaw_Polok ___________________ CERN - IT/CM/LCS _ _ > http://cern.ch/~jpolok ________ tel_+41_22_767_1834 _ > ______________________________________+41_75_411_9487 _ > > > > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > _______________________________________________ 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: 5780 bytes Desc: not available URL: From hhorak at redhat.com Wed Apr 26 15:47:07 2017 From: hhorak at redhat.com (Honza Horak) Date: Wed, 26 Apr 2017 17:47:07 +0200 Subject: [scl.org] Python3 (always latest) community SCL In-Reply-To: References: Message-ID: On 04/13/2017 04:27 PM, Tomas Orsava wrote: > Hi! > > On 04/11/2017 10:24 AM, Nick Coghlan wrote: >> I've been mulling this idea over for the past couple of weeks, and I'm >> wondering if it might make sense to create a rolling "sclo-python3" >> SCL, that's initially forked from >> https://www.softwarecollections.org/en/scls/rhscl/rh-python35/, but >> explicitly promises to rebase to new Python feature releases when they >> come out. >> >> So if people were happy to always run on the leading edge (even for >> X.Y.0 releases), they could use "sclo-python3", but if they wanted to >> stay on a particular X.Y release for a while, they would need to >> switch to the downstream rh-pythonXY SCLs. >> >> Remi, if I wanted to do that, where would I start? >> https://github.com/sclorg-distgit is useful as a reference for >> submitting changes to existing community SCLs, but it doesn't provide >> any guidance on how to start a new one (and that info is also missing >> from the wiki). > It would be great to have a state-of-the-art Python in Enterprise Linux, > but I think it would be better using the existing (though lacking > maintenance) Python 3 in EPEL [0] mechanism. > > While installing and using SCLs isn't hard, I think an RPM packaged > version is still easier for both maintenance and usage and people can > have EPEL packages built against it as well. In addition the transition > mechanism is smoother, as two Python versions are coexisting during the > transition period, whereas the rolling SCL would just switch and > everyone would have to immediately adjust. > > What would be the advantage of creating a rolling 'scl-python3' > collection over the EPEL mechanism [1]? I though I've already replied here, but obviously not.. One reason why rolling python3.x SCL might be better than EPEL is that some other projects within CentOS Build System might start using it, while EPEL packages are not generally usable there.. So, I'm not against if anyone would like to create such SCL, but I won't push on it either.. Honza > [0] https://fedoraproject.org/wiki/User:Bkabrda/EPEL7_Python3 > [1] https://admin.fedoraproject.org/pkgdb/package/rpms/python34/ > > All the best, > Tomas > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg