From Jaroslaw.Polok at cern.ch Thu Nov 5 10:38:03 2015 From: Jaroslaw.Polok at cern.ch (Jarek Polok) Date: Thu, 5 Nov 2015 11:38:03 +0100 Subject: [scl.org] bug reporting for slcs ? In-Reply-To: <56323644.8000702@cern.ch> References: <56323644.8000702@cern.ch> Message-ID: <563B318B.3070103@cern.ch> Since the problem is sclo-specific [ upstream package not affected ], submitted bug report here: https://bugs.centos.org/view.php?id=9705 (as 'Project Buildsys' category 'general') Cheers Jarek On 10/29/2015 04:07 PM, Jarek Polok wrote: > Hi, > > Where bugs for SCLo collections are to be reported ? > > bugs.centos.org does not seem to have SCLo project > defined ? > > We have just seen a (minor) bug in rh-ruby22 collection > (wrong shebang paths in some tools) > > My understanding is that that collection is a rebuilt > of upstream RH one: in that case the bug is to be > reported to CentOS/SCLo or to RH directly ? > > Thanks > > Jarek > > __ > ------------------------------------------------------- > _ Jaroslaw_Polok __________________ CERN - IT/OIS/WLS _ > _ 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/OIS/WLS _ _ http://cern.ch/~jpolok ________ tel_+41_22_767_1834 _ ______________________________________+41_75_411_9487 _ From mail-lists at karan.org Thu Nov 5 11:38:56 2015 From: mail-lists at karan.org (Karanbir Singh) Date: Thu, 5 Nov 2015 11:38:56 +0000 Subject: [scl.org] SCLo el6 packages have wrong upgrade path In-Reply-To: <5628C173.2020504@redhat.com> References: <56287696.50904@redhat.com> <5628BFF0.3010200@redhat.com> <5628C173.2020504@redhat.com> Message-ID: <563B3FD0.1000609@karan.org> On 22/10/15 11:58, Honza Horak wrote: > On 10/22/2015 12:52 PM, Karanbir Singh wrote: On 22/10/15 06:39, > Honza Horak wrote: >>>> So far I've just roughly looked at whether el6 SCL packages >>>> available at http://mirror.centos.org/centos/6/SCL/x86_64/ >>>> properly update to packages built in CBS, as we touched it >>>> yesterday. Long story short, there are packages with higher >>>> NVR than what we have in CBS now. >>>> >>>> There are basically two options here -- we may rebuild the >>>> problematic packages and bump release in CBS or we can >>>> document how to properly update using `yum distro-sync`. >>>> >>>> Anybody has a strong opinion about one of them? >>>> >>>> From my PoV, bumping&rebuilding should avoid more issues on >>>> users' side, because we can't be sure what happens if >>>> packages are combined (some from CBS and some from older >>>> repo) and depending on manual step won't work in 100% cases. >>>> >>>> Honza > > do we know why the versions are newer ? is the corrosponding code > also newer ? > >> I didn't check many packages, but the difference was only in >> release, so I expect there were issues during build and release >> was bumped because of that. But we should check whether the >> content is really the same. Not done so far. > is it possible to automate some of this ? it would be good to start getting the c6 content out as well -- Karanbir Singh, The CentOS Project, London, UK RH Ext. 8274455 | DID: 0044 207 009 4455 From hhorak at redhat.com Thu Nov 5 12:17:43 2015 From: hhorak at redhat.com (Honza Horak) Date: Thu, 5 Nov 2015 13:17:43 +0100 Subject: [scl.org] SCLo el6 packages have wrong upgrade path In-Reply-To: <563B3FD0.1000609@karan.org> References: <56287696.50904@redhat.com> <5628BFF0.3010200@redhat.com> <5628C173.2020504@redhat.com> <563B3FD0.1000609@karan.org> Message-ID: <563B48E7.20701@redhat.com> On 11/05/2015 12:38 PM, Karanbir Singh wrote: > On 22/10/15 11:58, Honza Horak wrote: >> On 10/22/2015 12:52 PM, Karanbir Singh wrote: On 22/10/15 06:39, >> Honza Horak wrote: >>>>> So far I've just roughly looked at whether el6 SCL packages >>>>> available at http://mirror.centos.org/centos/6/SCL/x86_64/ >>>>> properly update to packages built in CBS, as we touched it >>>>> yesterday. Long story short, there are packages with higher >>>>> NVR than what we have in CBS now. >>>>> >>>>> There are basically two options here -- we may rebuild the >>>>> problematic packages and bump release in CBS or we can >>>>> document how to properly update using `yum distro-sync`. >>>>> >>>>> Anybody has a strong opinion about one of them? >>>>> >>>>> From my PoV, bumping&rebuilding should avoid more issues on >>>>> users' side, because we can't be sure what happens if >>>>> packages are combined (some from CBS and some from older >>>>> repo) and depending on manual step won't work in 100% cases. >>>>> >>>>> Honza >> >> do we know why the versions are newer ? is the corrosponding code >> also newer ? >> >>> I didn't check many packages, but the difference was only in >>> release, so I expect there were issues during build and release >>> was bumped because of that. But we should check whether the >>> content is really the same. Not done so far. >> > > is it possible to automate some of this ? it would be good to start > getting the c6 content out as well > I believe it would, but I haven't look at it yet. I will try to look at it till Wednesday. Honza From hhorak at redhat.com Fri Nov 6 11:58:36 2015 From: hhorak at redhat.com (Honza Horak) Date: Fri, 6 Nov 2015 12:58:36 +0100 Subject: [scl.org] [CentOS-devel] Fwd: Re: bug reporting for slcs ? In-Reply-To: <563B3F62.80406@centos.org> References: <563B318B.3070103@cern.ch> <563B3F62.80406@centos.org> Message-ID: <563C95EC.8090500@redhat.com> Sorry for late response, I don't think we need anything on bugs.centos.org, we already have this space: https://bugzilla.redhat.com/enter_bug.cgi?product=softwarecollections.org Honza On 11/05/2015 12:37 PM, Karanbir Singh wrote: > Do we need a SCLo specific section on bugs.centos.org- and maybe get > Honza setup as primary developer for that ? > > regards, > > > -------- Forwarded Message -------- > Subject: Re: [scl.org] bug reporting for slcs ? > Date: Thu, 5 Nov 2015 11:38:03 +0100 > From: Jarek Polok > Organisation: CERN > To: sclorg at redhat.com > > Since the problem is sclo-specific [ upstream package > not affected ], submitted bug report here: > > https://bugs.centos.org/view.php?id=9705 > > (as 'Project Buildsys' category 'general') > > Cheers > > Jarek > > On 10/29/2015 04:07 PM, Jarek Polok wrote: >> Hi, >> >> Where bugs for SCLo collections are to be reported ? >> >> bugs.centos.org does not seem to have SCLo project >> defined ? >> >> We have just seen a (minor) bug in rh-ruby22 collection >> (wrong shebang paths in some tools) >> >> My understanding is that that collection is a rebuilt >> of upstream RH one: in that case the bug is to be >> reported to CentOS/SCLo or to RH directly ? >> >> Thanks >> >> Jarek >> >> __ >> ------------------------------------------------------- >> _ Jaroslaw_Polok __________________ CERN - IT/OIS/WLS _ >> _ 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 Jaroslaw.Polok at cern.ch Fri Nov 6 12:08:43 2015 From: Jaroslaw.Polok at cern.ch (Jarek Polok) Date: Fri, 6 Nov 2015 13:08:43 +0100 Subject: [scl.org] [CentOS-devel] Fwd: Re: bug reporting for slcs ? In-Reply-To: <563C95EC.8090500@redhat.com> References: <563B318B.3070103@cern.ch> <563B3F62.80406@centos.org> <563C95EC.8090500@redhat.com> Message-ID: <563C984B.9050306@cern.ch> On 11/06/2015 12:58 PM, Honza Horak wrote: > Sorry for late response, I don't think we need anything on > bugs.centos.org, we already have this space: > https://bugzilla.redhat.com/enter_bug.cgi?product=softwarecollections.org > But isn;t his one for official RH builds ? (the problem I did report concerns only CentOS rebuild of the upstream collection) And what about non-RH collections (vagrant1 for now as example ?) Best Regards Jarek > Honza > > On 11/05/2015 12:37 PM, Karanbir Singh wrote: >> Do we need a SCLo specific section on bugs.centos.org- and maybe get >> Honza setup as primary developer for that ? >> >> regards, >> >> >> -------- Forwarded Message -------- >> Subject: Re: [scl.org] bug reporting for slcs ? >> Date: Thu, 5 Nov 2015 11:38:03 +0100 >> From: Jarek Polok >> Organisation: CERN >> To: sclorg at redhat.com >> >> Since the problem is sclo-specific [ upstream package >> not affected ], submitted bug report here: >> >> https://bugs.centos.org/view.php?id=9705 >> >> (as 'Project Buildsys' category 'general') >> >> Cheers >> >> Jarek >> >> On 10/29/2015 04:07 PM, Jarek Polok wrote: >>> Hi, >>> >>> Where bugs for SCLo collections are to be reported ? >>> >>> bugs.centos.org does not seem to have SCLo project >>> defined ? >>> >>> We have just seen a (minor) bug in rh-ruby22 collection >>> (wrong shebang paths in some tools) >>> >>> My understanding is that that collection is a rebuilt >>> of upstream RH one: in that case the bug is to be >>> reported to CentOS/SCLo or to RH directly ? >>> >>> Thanks >>> >>> Jarek >>> >>> __ >>> ------------------------------------------------------- >>> _ Jaroslaw_Polok __________________ CERN - IT/OIS/WLS _ >>> _ 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/OIS/WLS _ _ http://cern.ch/~jpolok ________ tel_+41_22_767_1834 _ ______________________________________+41_75_411_9487 _ From hhorak at redhat.com Fri Nov 6 12:22:15 2015 From: hhorak at redhat.com (Honza Horak) Date: Fri, 6 Nov 2015 13:22:15 +0100 Subject: [scl.org] scl's release ? In-Reply-To: <5632326B.6070905@cern.ch> References: <5632326B.6070905@cern.ch> Message-ID: <563C9B77.4010701@redhat.com> We have slight problem with el6 packages, since there were already some builds before and in some cases there is no clean upgrade path, so we need to solve this first, then start to release. Generally, we planned to release the SCLs in batches, but I admit it doesn't always go according to plan, which was having all the collections be announced during November. We'll re-consider how this is going to be done on Monday and will let know here. The collections that we already tested are available already at: http://mirror.centos.org/centos-7/7/sclo/x86_64/rh/ The announcement will follow hopefully on Monday. Honza On 10/29/2015 03:51 PM, Jarek Polok wrote: > Hi all, > > Apologies if the question has been asked before ... but > I could not find the answer: > > When are SCLo collections going to be released ? > > I see that most packages are already built on > cbs.centos.org .. since few weeks ?) > > looking at the list archives I see there are > upgrade path problems for (some?) collections > on 6, but what about 7 ? > > Thanks > > Jarek > > __ > ------------------------------------------------------- > _ Jaroslaw_Polok __________________ CERN - IT/OIS/WLS _ > _ 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 Wed Nov 11 07:04:07 2015 From: hhorak at redhat.com (Honza Horak) Date: Wed, 11 Nov 2015 08:04:07 +0100 Subject: [scl.org] More recent nodejs In-Reply-To: References: Message-ID: <5642E867.5010100@redhat.com> AFAICT there are no plans to update 0.10 to 0.12 or including newer npm in existing nodejs010 SCL now. The focus moved more on 4.0. However, if you'd be willing to take a look at getting more updated nodejs010, we can discuss how to do it. Do you have any concrete ideas what would be the changes? Honza On 10/21/2015 11:28 PM, Davis, Daniel (NIH/NLM) [C] wrote: > What are the plans, if any, to update nodejs? Is this something you > guys could accept help with? > > Dan Davis, Systems/Applications Architect (Contractor), > > Office of Computer and Communications Systems, > > National Library of Medicine, NIH > > > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > From hhorak at redhat.com Wed Nov 11 07:06:25 2015 From: hhorak at redhat.com (Honza Horak) Date: Wed, 11 Nov 2015 08:06:25 +0100 Subject: [scl.org] [CentOS-devel] Fwd: Re: bug reporting for slcs ? In-Reply-To: <563C984B.9050306@cern.ch> References: <563B318B.3070103@cern.ch> <563B3F62.80406@centos.org> <563C95EC.8090500@redhat.com> <563C984B.9050306@cern.ch> Message-ID: <5642E8F1.6000507@redhat.com> On 11/06/2015 01:08 PM, Jarek Polok wrote: > On 11/06/2015 12:58 PM, Honza Horak wrote: >> Sorry for late response, I don't think we need anything on >> bugs.centos.org, we already have this space: >> https://bugzilla.redhat.com/enter_bug.cgi?product=softwarecollections.org >> > > But isn;t his one for official RH builds ? No, this one is exactly for the centos rebuilds, for official RH builds there is: https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Software%20Collections > (the problem I did report concerns only CentOS rebuild > of the upstream collection) > And what about non-RH collections (vagrant1 for now as example ?) non-RH collections should be part of the softwarecollections.org BZ product as well (scl-vagrant1 is there already): https://bugzilla.redhat.com/enter_bug.cgi?product=softwarecollections.org Honza > Best Regards > > Jarek > > >> Honza >> >> On 11/05/2015 12:37 PM, Karanbir Singh wrote: >>> Do we need a SCLo specific section on bugs.centos.org- and maybe get >>> Honza setup as primary developer for that ? >>> >>> regards, >>> >>> >>> -------- Forwarded Message -------- >>> Subject: Re: [scl.org] bug reporting for slcs ? >>> Date: Thu, 5 Nov 2015 11:38:03 +0100 >>> From: Jarek Polok >>> Organisation: CERN >>> To: sclorg at redhat.com >>> >>> Since the problem is sclo-specific [ upstream package >>> not affected ], submitted bug report here: >>> >>> https://bugs.centos.org/view.php?id=9705 >>> >>> (as 'Project Buildsys' category 'general') >>> >>> Cheers >>> >>> Jarek >>> >>> On 10/29/2015 04:07 PM, Jarek Polok wrote: >>>> Hi, >>>> >>>> Where bugs for SCLo collections are to be reported ? >>>> >>>> bugs.centos.org does not seem to have SCLo project >>>> defined ? >>>> >>>> We have just seen a (minor) bug in rh-ruby22 collection >>>> (wrong shebang paths in some tools) >>>> >>>> My understanding is that that collection is a rebuilt >>>> of upstream RH one: in that case the bug is to be >>>> reported to CentOS/SCLo or to RH directly ? >>>> >>>> Thanks >>>> >>>> Jarek >>>> >>>> __ >>>> ------------------------------------------------------- >>>> _ Jaroslaw_Polok __________________ CERN - IT/OIS/WLS _ >>>> _ 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 > > From tsorensen at gmail.com Sat Nov 7 12:36:58 2015 From: tsorensen at gmail.com (Tom Sorensen) Date: Sat, 7 Nov 2015 07:36:58 -0500 Subject: [scl.org] [CentOS-devel] Fwd: Re: bug reporting for slcs ? In-Reply-To: <563C95EC.8090500@redhat.com> References: <563B318B.3070103@cern.ch> <563B3F62.80406@centos.org> <563C95EC.8090500@redhat.com> Message-ID: While I'm fine with this, it does create a split between where most CentOS bugs are filed and where the scl-sig ones are filed. Perhaps an excuse to revisit unifying the bug reporting? On Friday, November 6, 2015, Honza Horak wrote: > Sorry for late response, I don't think we need anything on bugs.centos.org, > we already have this space: > https://bugzilla.redhat.com/enter_bug.cgi?product=softwarecollections.org > > Honza > > On 11/05/2015 12:37 PM, Karanbir Singh wrote: > >> Do we need a SCLo specific section on bugs.centos.org- and maybe get >> Honza setup as primary developer for that ? >> >> regards, >> >> >> -------- Forwarded Message -------- >> Subject: Re: [scl.org] bug reporting for slcs ? >> Date: Thu, 5 Nov 2015 11:38:03 +0100 >> From: Jarek Polok >> Organisation: CERN >> To: sclorg at redhat.com >> >> Since the problem is sclo-specific [ upstream package >> not affected ], submitted bug report here: >> >> https://bugs.centos.org/view.php?id=9705 >> >> (as 'Project Buildsys' category 'general') >> >> Cheers >> >> Jarek >> >> On 10/29/2015 04:07 PM, Jarek Polok wrote: >> >>> Hi, >>> >>> Where bugs for SCLo collections are to be reported ? >>> >>> bugs.centos.org does not seem to have SCLo project >>> defined ? >>> >>> We have just seen a (minor) bug in rh-ruby22 collection >>> (wrong shebang paths in some tools) >>> >>> My understanding is that that collection is a rebuilt >>> of upstream RH one: in that case the bug is to be >>> reported to CentOS/SCLo or to RH directly ? >>> >>> Thanks >>> >>> Jarek >>> >>> __ >>> ------------------------------------------------------- >>> _ Jaroslaw_Polok __________________ CERN - IT/OIS/WLS _ >>> _ 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 >>> >> >> >> _______________________________________________ > CentOS-devel mailing list > CentOS-devel at centos.org > https://lists.centos.org/mailman/listinfo/centos-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hhorak at redhat.com Wed Nov 11 08:55:41 2015 From: hhorak at redhat.com (Honza Horak) Date: Wed, 11 Nov 2015 09:55:41 +0100 Subject: [scl.org] [CentOS-devel] Fwd: Re: bug reporting for slcs ? In-Reply-To: References: <563B318B.3070103@cern.ch> <563B3F62.80406@centos.org> <563C95EC.8090500@redhat.com> Message-ID: <5643028D.8050201@redhat.com> I see, but on the other hand it gives us ability to clone bugs to RHSCL product since many issues in centos collections will be reproducible in RHSCL packages as well. With other packages that are rebuilt in centos (non-SCL), people report issues into bugzilla.redhat.com as well, don't they? Honza On 11/07/2015 01:36 PM, Tom Sorensen wrote: > While I'm fine with this, it does create a split between where most > CentOS bugs are filed and where the scl-sig ones are filed. > > Perhaps an excuse to revisit unifying the bug reporting? > > On Friday, November 6, 2015, Honza Horak > wrote: > > Sorry for late response, I don't think we need anything on > bugs.centos.org , we already have this space: > https://bugzilla.redhat.com/enter_bug.cgi?product=softwarecollections.org > > Honza > > On 11/05/2015 12:37 PM, Karanbir Singh wrote: > > Do we need a SCLo specific section on bugs.centos.org- and maybe get > Honza setup as primary developer for that ? > > regards, > > > -------- Forwarded Message -------- > Subject: Re: [scl.org ] bug reporting for slcs ? > Date: Thu, 5 Nov 2015 11:38:03 +0100 > From: Jarek Polok > Organisation: CERN > To: sclorg at redhat.com > > Since the problem is sclo-specific [ upstream package > not affected ], submitted bug report here: > > https://bugs.centos.org/view.php?id=9705 > > (as 'Project Buildsys' category 'general') > > Cheers > > Jarek > > On 10/29/2015 04:07 PM, Jarek Polok wrote: > > Hi, > > Where bugs for SCLo collections are to be reported ? > > bugs.centos.org does not seem to > have SCLo project > defined ? > > We have just seen a (minor) bug in rh-ruby22 collection > (wrong shebang paths in some tools) > > My understanding is that that collection is a rebuilt > of upstream RH one: in that case the bug is to be > reported to CentOS/SCLo or to RH directly ? > > Thanks > > Jarek > > __ > ------------------------------------------------------- > _ Jaroslaw_Polok __________________ CERN - IT/OIS/WLS _ > _ 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 > > > > _______________________________________________ > CentOS-devel mailing list > CentOS-devel at centos.org > https://lists.centos.org/mailman/listinfo/centos-devel > > > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > From hhorak at redhat.com Wed Nov 11 16:43:22 2015 From: hhorak at redhat.com (Honza Horak) Date: Wed, 11 Nov 2015 17:43:22 +0100 Subject: [scl.org] Announcing release for Vagrant 1.7.4 on CentOS Linux 7 x86_64 SCL Message-ID: <5643702A.6090405@redhat.com> I am pleased to announce the immediate availability of Vagrant 1.7.4 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl $ sudo yum install sclo-vagrant1 $ scl enable sclo-vagrant1 bash At this point you should be able to use vagrant just as a normal application. An example work-flow might be: $ vagrant init centos/7 $ vagrant up $ vagrant ssh In order to view the individual components included in this collection, including additional vagrant plugins, you can run : $ sudo yum list sclo-vagrant\* About Software Collections -------------------------- Software Collections give you the power to build, install, and use multiple versions of software on the same system, without affecting system-wide installed packages. Each collection is delivered as a group of RPMs, with the grouping being done using the name of the collection as a prefix of all packages that are part of the software collection. The collection sclo-vagrant1 delivers a Vagrant tool in version 1.x that allows to create and configure virtual development environments. Some of the most common plugins are also included in the collection as RPMs. The sclo-vagrant1 collection relies on the following additional collections which will also be installed: rh-ruby22, rh-ror41 For more on the Vagrant tool and other plugins, see https://www.vagrantup.com. The SCLo SIG in CentOS ---------------------- The Software Collections SIG group is an open community group co-ordinating the development of the SCL technology, and helping curate a reference set of collections. In addition to the Vagrant collection being released here, we also build and deliver databases, web servers, and language stacks including multiple versions of PostgreSQL, MariaDB, Apache HTTP Server, Ruby, NodeJS, Python and others. Software Collections SIG release was announced at https://lists.centos.org/pipermail/centos-announce/2015-October/021446.html You can learn more about Software Collections concepts at: http://softwarecollections.org/ You can find information on the SIG at https://wiki.centos.org/SpecialInterestGroup/SCLo ; this includes howto get involved and help with the effort. We meet every Wednesday at 16:00 UTC in #centos-devel (ref: https://www.centos.org/community/calendar), for an informal open forum open to anyone who might have comments, concerns or wants to get started with SCL's in CentOS. Enjoy! Honza SCLo SIG member From hhorak at redhat.com Thu Nov 12 17:34:10 2015 From: hhorak at redhat.com (Honza Horak) Date: Thu, 12 Nov 2015 18:34:10 +0100 Subject: [scl.org] Announcing release for Ruby 1.9.3, 2.0.0, 2.2 and Ruby on Rails 3.2, 4.0, 4.1 on CentOS Linux 7 x86_64 SCL Message-ID: <5644CD92.6040707@redhat.com> I am pleased to announce the immediate availability of Ruby in versions 1.9.3, 2.0.0, and 2.2, and Ruby on Rails in versions 3.2, 4.0 and 4.1 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps (example of Ruby 2.2 and Ruby on Rails 4.1, for others use particular collection names instead): $ sudo yum install centos-release-scl $ sudo yum install rh-ruby22 rh-ror41 $ scl enable rh-ruby22 bash At this point you should be able to use ruby just as a normal application. An examples of commands run might be: $ ruby my-app.rb $ gem install activeresource $ bundle In order to view the individual components included in this collection, including additional rubygems plugins, you can run: $ sudo yum list rh-ruby22\* rh-ror41\* The rh-ror41 collection relies on the rh-ruby22 collection and the ror40 collection relies on the ruby200 collection, so the Ruby collections will be also installed when the Ruby on Rails collection is installed. About Software Collections -------------------------- Software Collections give you the power to build, install, and use multiple versions of software on the same system, without affecting system-wide installed packages. Each collection is delivered as a group of RPMs, with the grouping being done using the name of the collection as a prefix of all packages that are part of the software collection. The collection rh-ruby22 delivers bundler and Ruby interpreter in version 2.2, while the collection rh-ror41 delivers Ruby on Rails framework in version 4.1 that allows to create and run applications in Ruby or Ruby on Rails framework. The collection ruby200 delivers only the Ruby interpreter in version 2.0.0, while the ror40 collection delivers Ruby on Rails framework in versoin 4.0 and bundler. The collection ruby193 delivers Ruby interpreter in version 1.9.3, bundler and Ruby on Rails framework in version 3.2. Some of the most common rubygems are also included in the collections as RPMs, the rest may be installed using bundler or gem tools. For more on the Ruby and Ruby on Rails, see https://www.ruby-lang.org, http://rubyonrails.org or https://rubygems.org. The SCLo SIG in CentOS ---------------------- The Software Collections SIG group is an open community group co-ordinating the development of the SCL technology, and helping curate a reference set of collections. In addition to the Ruby and Ruby on Rails collections being released here, we also build and deliver databases, web servers, and language stacks including multiple versions of PostgreSQL, MariaDB, Apache HTTP Server, NodeJS, Python and others. Software Collections SIG release was announced at https://lists.centos.org/pipermail/centos-announce/2015-October/021446.html You can learn more about Software Collections concepts at: http://softwarecollections.org You can find information on the SIG at https://wiki.centos.org/SpecialInterestGroup/SCLo ; this includes howto get involved and help with the effort. We meet every Wednesday at 16:00 UTC in #centos-devel (ref: https://www.centos.org/community/calendar), for an informal open forum open to anyone who might have comments, concerns or wants to get started with SCL's in CentOS. Enjoy! Honza SCLo SIG member From noah at coderanger.net Thu Nov 12 17:39:47 2015 From: noah at coderanger.net (Noah Kantrowitz) Date: Thu, 12 Nov 2015 09:39:47 -0800 Subject: [scl.org] Announcing release for Ruby 1.9.3, 2.0.0, 2.2 and Ruby on Rails 3.2, 4.0, 4.1 on CentOS Linux 7 x86_64 SCL In-Reply-To: <5644CD92.6040707@redhat.com> References: <5644CD92.6040707@redhat.com> Message-ID: For the uninitiated, how do these differ from the existing EL7 builds of those packages? --Noah > On Nov 12, 2015, at 9:34 AM, Honza Horak wrote: > > I am pleased to announce the immediate availability of Ruby in versions 1.9.3, 2.0.0, and 2.2, and Ruby on Rails in versions 3.2, 4.0 and 4.1 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). > > QuickStart > ---------- > You can get started in three easy steps (example of Ruby 2.2 and Ruby on Rails 4.1, for others use particular collection names instead): > $ sudo yum install centos-release-scl > $ sudo yum install rh-ruby22 rh-ror41 > $ scl enable rh-ruby22 bash > > At this point you should be able to use ruby just as a normal > application. An examples of commands run might be: > $ ruby my-app.rb > $ gem install activeresource > $ bundle > > In order to view the individual components included in this > collection, including additional rubygems plugins, you can run: > $ sudo yum list rh-ruby22\* rh-ror41\* > > The rh-ror41 collection relies on the rh-ruby22 collection and the ror40 collection relies on the ruby200 collection, so the Ruby collections will be also installed when the Ruby on Rails collection is installed. > > About Software Collections > -------------------------- > Software Collections give you the power to build, install, and use multiple versions of software on the same system, without affecting system-wide installed packages. Each collection is delivered as a group of RPMs, with the grouping being done using the name of the collection as a prefix of all packages that are part of the software collection. > > The collection rh-ruby22 delivers bundler and Ruby interpreter in version 2.2, while the collection rh-ror41 delivers Ruby on Rails framework in version 4.1 that allows to create and run applications in Ruby or Ruby on Rails framework. > > The collection ruby200 delivers only the Ruby interpreter in version 2.0.0, while the ror40 collection delivers Ruby on Rails framework in versoin 4.0 and bundler. > > The collection ruby193 delivers Ruby interpreter in version 1.9.3, bundler and Ruby on Rails framework in version 3.2. > > Some of the most common rubygems are also included in the collections as RPMs, the rest may be installed using bundler or gem tools. > > For more on the Ruby and Ruby on Rails, see https://www.ruby-lang.org, http://rubyonrails.org or https://rubygems.org. > > The SCLo SIG in CentOS > ---------------------- > The Software Collections SIG group is an open community group co-ordinating the development of the SCL technology, and helping curate a reference set of collections. In addition to the Ruby and Ruby on Rails collections being released here, we also build and deliver databases, web servers, and language stacks including multiple versions of PostgreSQL, MariaDB, Apache HTTP Server, NodeJS, Python and others. > > Software Collections SIG release was announced at https://lists.centos.org/pipermail/centos-announce/2015-October/021446.html > > You can learn more about Software Collections concepts at: http://softwarecollections.org > You can find information on the SIG at https://wiki.centos.org/SpecialInterestGroup/SCLo ; this includes howto get involved and help with the effort. > > We meet every Wednesday at 16:00 UTC in #centos-devel (ref: https://www.centos.org/community/calendar), for an informal open forum open to anyone who might have comments, concerns or wants to get started with SCL's in CentOS. > > Enjoy! > > Honza > SCLo SIG member > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 163 bytes Desc: Message signed with OpenPGP using GPGMail URL: From hhorak at redhat.com Thu Nov 12 18:08:54 2015 From: hhorak at redhat.com (Honza Horak) Date: Thu, 12 Nov 2015 19:08:54 +0100 Subject: [scl.org] Announcing release for Ruby 1.9.3, 2.0.0, 2.2 and Ruby on Rails 3.2, 4.0, 4.1 on CentOS Linux 7 x86_64 SCL In-Reply-To: References: <5644CD92.6040707@redhat.com> Message-ID: <5644D5B6.4010800@redhat.com> Big difference is that these packages are build in CBS (cbs.centos.org), so they can be used for other CentOS projects. Plus there are some packages that haven't been updated in http://copr.fedoraproject.org so there are slightly newer version built in CBS. Otherwise, it should be quite same content-wise, but we believe CentOS is better place for such content. Honza On 11/12/2015 06:39 PM, Noah Kantrowitz wrote: > For the uninitiated, how do these differ from the existing EL7 builds of those packages? > > --Noah > >> On Nov 12, 2015, at 9:34 AM, Honza Horak wrote: >> >> I am pleased to announce the immediate availability of Ruby in versions 1.9.3, 2.0.0, and 2.2, and Ruby on Rails in versions 3.2, 4.0 and 4.1 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). >> >> QuickStart >> ---------- >> You can get started in three easy steps (example of Ruby 2.2 and Ruby on Rails 4.1, for others use particular collection names instead): >> $ sudo yum install centos-release-scl >> $ sudo yum install rh-ruby22 rh-ror41 >> $ scl enable rh-ruby22 bash >> >> At this point you should be able to use ruby just as a normal >> application. An examples of commands run might be: >> $ ruby my-app.rb >> $ gem install activeresource >> $ bundle >> >> In order to view the individual components included in this >> collection, including additional rubygems plugins, you can run: >> $ sudo yum list rh-ruby22\* rh-ror41\* >> >> The rh-ror41 collection relies on the rh-ruby22 collection and the ror40 collection relies on the ruby200 collection, so the Ruby collections will be also installed when the Ruby on Rails collection is installed. >> >> About Software Collections >> -------------------------- >> Software Collections give you the power to build, install, and use multiple versions of software on the same system, without affecting system-wide installed packages. Each collection is delivered as a group of RPMs, with the grouping being done using the name of the collection as a prefix of all packages that are part of the software collection. >> >> The collection rh-ruby22 delivers bundler and Ruby interpreter in version 2.2, while the collection rh-ror41 delivers Ruby on Rails framework in version 4.1 that allows to create and run applications in Ruby or Ruby on Rails framework. >> >> The collection ruby200 delivers only the Ruby interpreter in version 2.0.0, while the ror40 collection delivers Ruby on Rails framework in versoin 4.0 and bundler. >> >> The collection ruby193 delivers Ruby interpreter in version 1.9.3, bundler and Ruby on Rails framework in version 3.2. >> >> Some of the most common rubygems are also included in the collections as RPMs, the rest may be installed using bundler or gem tools. >> >> For more on the Ruby and Ruby on Rails, see https://www.ruby-lang.org, http://rubyonrails.org or https://rubygems.org. >> >> The SCLo SIG in CentOS >> ---------------------- >> The Software Collections SIG group is an open community group co-ordinating the development of the SCL technology, and helping curate a reference set of collections. In addition to the Ruby and Ruby on Rails collections being released here, we also build and deliver databases, web servers, and language stacks including multiple versions of PostgreSQL, MariaDB, Apache HTTP Server, NodeJS, Python and others. >> >> Software Collections SIG release was announced at https://lists.centos.org/pipermail/centos-announce/2015-October/021446.html >> >> You can learn more about Software Collections concepts at: http://softwarecollections.org >> You can find information on the SIG at https://wiki.centos.org/SpecialInterestGroup/SCLo ; this includes howto get involved and help with the effort. >> >> We meet every Wednesday at 16:00 UTC in #centos-devel (ref: https://www.centos.org/community/calendar), for an informal open forum open to anyone who might have comments, concerns or wants to get started with SCL's in CentOS. >> >> Enjoy! >> >> Honza >> SCLo SIG member >> >> _______________________________________________ >> SCLorg mailing list >> SCLorg at redhat.com >> https://www.redhat.com/mailman/listinfo/sclorg > From noah at coderanger.net Thu Nov 12 18:36:03 2015 From: noah at coderanger.net (Noah Kantrowitz) Date: Thu, 12 Nov 2015 10:36:03 -0800 Subject: [scl.org] Announcing release for Ruby 1.9.3, 2.0.0, 2.2 and Ruby on Rails 3.2, 4.0, 4.1 on CentOS Linux 7 x86_64 SCL In-Reply-To: <5644D5B6.4010800@redhat.com> References: <5644CD92.6040707@redhat.com> <5644D5B6.4010800@redhat.com> Message-ID: <9EBA963D-20EF-4532-A407-A62D9C6E9B52@coderanger.net> I guess I should ask more specifically, are they expected to remain cross-compatible forever? I maintain a bunch of the low-level Chef cookbook which offer SCL as an install strategy. They are currently using the RHEL6/7 builds, do I need to write separate test cases for the CentOS versions? --Noah > On Nov 12, 2015, at 10:08 AM, Honza Horak wrote: > > Big difference is that these packages are build in CBS (cbs.centos.org), so they can be used for other CentOS projects. Plus there are some packages that haven't been updated in http://copr.fedoraproject.org so there are slightly newer version built in CBS. Otherwise, it should be quite same content-wise, but we believe CentOS is better place for such content. > > Honza > > On 11/12/2015 06:39 PM, Noah Kantrowitz wrote: >> For the uninitiated, how do these differ from the existing EL7 builds of those packages? >> >> --Noah >> >>> On Nov 12, 2015, at 9:34 AM, Honza Horak wrote: >>> >>> I am pleased to announce the immediate availability of Ruby in versions 1.9.3, 2.0.0, and 2.2, and Ruby on Rails in versions 3.2, 4.0 and 4.1 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). >>> >>> QuickStart >>> ---------- >>> You can get started in three easy steps (example of Ruby 2.2 and Ruby on Rails 4.1, for others use particular collection names instead): >>> $ sudo yum install centos-release-scl >>> $ sudo yum install rh-ruby22 rh-ror41 >>> $ scl enable rh-ruby22 bash >>> >>> At this point you should be able to use ruby just as a normal >>> application. An examples of commands run might be: >>> $ ruby my-app.rb >>> $ gem install activeresource >>> $ bundle >>> >>> In order to view the individual components included in this >>> collection, including additional rubygems plugins, you can run: >>> $ sudo yum list rh-ruby22\* rh-ror41\* >>> >>> The rh-ror41 collection relies on the rh-ruby22 collection and the ror40 collection relies on the ruby200 collection, so the Ruby collections will be also installed when the Ruby on Rails collection is installed. >>> >>> About Software Collections >>> -------------------------- >>> Software Collections give you the power to build, install, and use multiple versions of software on the same system, without affecting system-wide installed packages. Each collection is delivered as a group of RPMs, with the grouping being done using the name of the collection as a prefix of all packages that are part of the software collection. >>> >>> The collection rh-ruby22 delivers bundler and Ruby interpreter in version 2.2, while the collection rh-ror41 delivers Ruby on Rails framework in version 4.1 that allows to create and run applications in Ruby or Ruby on Rails framework. >>> >>> The collection ruby200 delivers only the Ruby interpreter in version 2.0.0, while the ror40 collection delivers Ruby on Rails framework in versoin 4.0 and bundler. >>> >>> The collection ruby193 delivers Ruby interpreter in version 1.9.3, bundler and Ruby on Rails framework in version 3.2. >>> >>> Some of the most common rubygems are also included in the collections as RPMs, the rest may be installed using bundler or gem tools. >>> >>> For more on the Ruby and Ruby on Rails, see https://www.ruby-lang.org, http://rubyonrails.org or https://rubygems.org. >>> >>> The SCLo SIG in CentOS >>> ---------------------- >>> The Software Collections SIG group is an open community group co-ordinating the development of the SCL technology, and helping curate a reference set of collections. In addition to the Ruby and Ruby on Rails collections being released here, we also build and deliver databases, web servers, and language stacks including multiple versions of PostgreSQL, MariaDB, Apache HTTP Server, NodeJS, Python and others. >>> >>> Software Collections SIG release was announced at https://lists.centos.org/pipermail/centos-announce/2015-October/021446.html >>> >>> You can learn more about Software Collections concepts at: http://softwarecollections.org >>> You can find information on the SIG at https://wiki.centos.org/SpecialInterestGroup/SCLo ; this includes howto get involved and help with the effort. >>> >>> We meet every Wednesday at 16:00 UTC in #centos-devel (ref: https://www.centos.org/community/calendar), for an informal open forum open to anyone who might have comments, concerns or wants to get started with SCL's in CentOS. >>> >>> Enjoy! >>> >>> Honza >>> SCLo SIG member >>> >>> _______________________________________________ >>> SCLorg mailing list >>> SCLorg at redhat.com >>> https://www.redhat.com/mailman/listinfo/sclorg >> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 163 bytes Desc: Message signed with OpenPGP using GPGMail URL: From hhorak at redhat.com Thu Nov 12 19:09:26 2015 From: hhorak at redhat.com (Honza Horak) Date: Thu, 12 Nov 2015 20:09:26 +0100 Subject: [scl.org] Announcing release for Ruby 1.9.3, 2.0.0, 2.2 and Ruby on Rails 3.2, 4.0, 4.1 on CentOS Linux 7 x86_64 SCL In-Reply-To: <9EBA963D-20EF-4532-A407-A62D9C6E9B52@coderanger.net> References: <5644CD92.6040707@redhat.com> <5644D5B6.4010800@redhat.com> <9EBA963D-20EF-4532-A407-A62D9C6E9B52@coderanger.net> Message-ID: <5644E3E6.1040501@redhat.com> I'm not aware about any incompatibilities, they should be really the same. Honza On 11/12/2015 07:36 PM, Noah Kantrowitz wrote: > I guess I should ask more specifically, are they expected to remain cross-compatible forever? I maintain a bunch of the low-level Chef cookbook which offer SCL as an install strategy. They are currently using the RHEL6/7 builds, do I need to write separate test cases for the CentOS versions? > > --Noah > >> On Nov 12, 2015, at 10:08 AM, Honza Horak wrote: >> >> Big difference is that these packages are build in CBS (cbs.centos.org), so they can be used for other CentOS projects. Plus there are some packages that haven't been updated in http://copr.fedoraproject.org so there are slightly newer version built in CBS. Otherwise, it should be quite same content-wise, but we believe CentOS is better place for such content. >> >> Honza >> >> On 11/12/2015 06:39 PM, Noah Kantrowitz wrote: >>> For the uninitiated, how do these differ from the existing EL7 builds of those packages? >>> >>> --Noah >>> >>>> On Nov 12, 2015, at 9:34 AM, Honza Horak wrote: >>>> >>>> I am pleased to announce the immediate availability of Ruby in versions 1.9.3, 2.0.0, and 2.2, and Ruby on Rails in versions 3.2, 4.0 and 4.1 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). >>>> >>>> QuickStart >>>> ---------- >>>> You can get started in three easy steps (example of Ruby 2.2 and Ruby on Rails 4.1, for others use particular collection names instead): >>>> $ sudo yum install centos-release-scl >>>> $ sudo yum install rh-ruby22 rh-ror41 >>>> $ scl enable rh-ruby22 bash >>>> >>>> At this point you should be able to use ruby just as a normal >>>> application. An examples of commands run might be: >>>> $ ruby my-app.rb >>>> $ gem install activeresource >>>> $ bundle >>>> >>>> In order to view the individual components included in this >>>> collection, including additional rubygems plugins, you can run: >>>> $ sudo yum list rh-ruby22\* rh-ror41\* >>>> >>>> The rh-ror41 collection relies on the rh-ruby22 collection and the ror40 collection relies on the ruby200 collection, so the Ruby collections will be also installed when the Ruby on Rails collection is installed. >>>> >>>> About Software Collections >>>> -------------------------- >>>> Software Collections give you the power to build, install, and use multiple versions of software on the same system, without affecting system-wide installed packages. Each collection is delivered as a group of RPMs, with the grouping being done using the name of the collection as a prefix of all packages that are part of the software collection. >>>> >>>> The collection rh-ruby22 delivers bundler and Ruby interpreter in version 2.2, while the collection rh-ror41 delivers Ruby on Rails framework in version 4.1 that allows to create and run applications in Ruby or Ruby on Rails framework. >>>> >>>> The collection ruby200 delivers only the Ruby interpreter in version 2.0.0, while the ror40 collection delivers Ruby on Rails framework in versoin 4.0 and bundler. >>>> >>>> The collection ruby193 delivers Ruby interpreter in version 1.9.3, bundler and Ruby on Rails framework in version 3.2. >>>> >>>> Some of the most common rubygems are also included in the collections as RPMs, the rest may be installed using bundler or gem tools. >>>> >>>> For more on the Ruby and Ruby on Rails, see https://www.ruby-lang.org, http://rubyonrails.org or https://rubygems.org. >>>> >>>> The SCLo SIG in CentOS >>>> ---------------------- >>>> The Software Collections SIG group is an open community group co-ordinating the development of the SCL technology, and helping curate a reference set of collections. In addition to the Ruby and Ruby on Rails collections being released here, we also build and deliver databases, web servers, and language stacks including multiple versions of PostgreSQL, MariaDB, Apache HTTP Server, NodeJS, Python and others. >>>> >>>> Software Collections SIG release was announced at https://lists.centos.org/pipermail/centos-announce/2015-October/021446.html >>>> >>>> You can learn more about Software Collections concepts at: http://softwarecollections.org >>>> You can find information on the SIG at https://wiki.centos.org/SpecialInterestGroup/SCLo ; this includes howto get involved and help with the effort. >>>> >>>> We meet every Wednesday at 16:00 UTC in #centos-devel (ref: https://www.centos.org/community/calendar), for an informal open forum open to anyone who might have comments, concerns or wants to get started with SCL's in CentOS. >>>> >>>> Enjoy! >>>> >>>> Honza >>>> SCLo SIG member >>>> >>>> _______________________________________________ >>>> SCLorg mailing list >>>> SCLorg at redhat.com >>>> https://www.redhat.com/mailman/listinfo/sclorg >>> > From Michael.Ward at melbourneit.com.au Fri Nov 13 01:08:12 2015 From: Michael.Ward at melbourneit.com.au (Michael Ward) Date: Fri, 13 Nov 2015 01:08:12 +0000 Subject: [scl.org] GPG Keys for Signed Packages Message-ID: Hi, We push updates to our CentOS 6/7 servers via Spacewalk. At the moment we have a custom channel created for SCL content and are sync'ing down just a couple of repositories that we are interested in (httpd24 and php55). However when trying to push updates via Spacewalk we run into issues that the servers with these packages don't have the necessary GPG keys installed. I am aware that we could manually override on each server so that the scl channel doesn't require GPG keys, but since the packages are signed I'd prefer to use this signature. I've hunted around the SCL website but haven't managed to find any GPG public keys for importing.. Are the public keys for the packages available somewhere and I'm just missing them ? Ideally I'd like to know where to find all the keys in case we add extra software collections to our channel later, but for now at a minimum are these keys available: Httpd24 - Signature : RSA/SHA1, Tue Feb 17 01:51:07 2015, Key ID eaddec352d035be8 Php55 - Signature : RSA/SHA1, Tue Jun 9 03:04:29 2015, Key ID fd0cba1158446831 Regards, Michael Ward. From ppisar at redhat.com Fri Nov 13 06:40:46 2015 From: ppisar at redhat.com (Petr Pisar) Date: Fri, 13 Nov 2015 07:40:46 +0100 Subject: [scl.org] GPG Keys for Signed Packages In-Reply-To: References: Message-ID: <20151113064045.GB2158@dhcp-0-146.brq.redhat.com> On Fri, Nov 13, 2015 at 01:08:12AM +0000, Michael Ward wrote: > I've hunted around the SCL website but haven't managed to find any GPG > public keys for importing.. > > Are the public keys for the packages available somewhere and I'm just > missing them ? > See . -- Petr -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 213 bytes Desc: not available URL: From ncoghlan at redhat.com Fri Nov 13 06:50:34 2015 From: ncoghlan at redhat.com (Nick Coghlan) Date: Fri, 13 Nov 2015 16:50:34 +1000 Subject: [scl.org] Announcing release for Ruby 1.9.3, 2.0.0, 2.2 and Ruby on Rails 3.2, 4.0, 4.1 on CentOS Linux 7 x86_64 SCL In-Reply-To: <5644E3E6.1040501@redhat.com> References: <5644CD92.6040707@redhat.com> <5644D5B6.4010800@redhat.com> <9EBA963D-20EF-4532-A407-A62D9C6E9B52@coderanger.net> <5644E3E6.1040501@redhat.com> Message-ID: On Fri, Nov 13, 2015 at 5:09 AM, Honza Horak wrote: > I'm not aware about any incompatibilities, they should be really the same. If I'm reading it correctly, I don't think Noah's question is about these specific versions, I think it's about the ongoing maintenance plans for how the CentOS-built community SCLs relate to the Red Hat SCL product. My own understanding is that the intent is for them to share source code just as CentOS and RHEL do, with the differences being in where they're built (CentOS community infrastructure vs Red Hat's certified infrastructure) and the lack of commercial support from Red Hat for the community versions. The main thing changing with the move to using cbs.centos.org is that there's now a clear upstream home for the softwarecollections.org build process, rather than the relatively ad hoc approach that needed to be adopted after Fedora's Engineering Steering Council rejected the use of Fedora's infrastructure for that purpose. Regards, Nick. -- Nick Coghlan Fedora Environments & Stacks Red Hat Developer Experience, Brisbane Software Development Workflow Designer & Process Architect From hhorak at redhat.com Fri Nov 13 06:54:56 2015 From: hhorak at redhat.com (Honza Horak) Date: Fri, 13 Nov 2015 07:54:56 +0100 Subject: [scl.org] Announcing release for Ruby 1.9.3, 2.0.0, 2.2 and Ruby on Rails 3.2, 4.0, 4.1 on CentOS Linux 7 x86_64 SCL In-Reply-To: References: <5644CD92.6040707@redhat.com> <5644D5B6.4010800@redhat.com> <9EBA963D-20EF-4532-A407-A62D9C6E9B52@coderanger.net> <5644E3E6.1040501@redhat.com> Message-ID: <56458940.3040402@redhat.com> Yeah, it is as Nick wrote, so if the question asked for that, bellow is the answer. Honza On 11/13/2015 07:50 AM, Nick Coghlan wrote: > On Fri, Nov 13, 2015 at 5:09 AM, Honza Horak wrote: >> I'm not aware about any incompatibilities, they should be really the same. > > If I'm reading it correctly, I don't think Noah's question is about > these specific versions, I think it's about the ongoing maintenance > plans for how the CentOS-built community SCLs relate to the Red Hat > SCL product. > > My own understanding is that the intent is for them to share source > code just as CentOS and RHEL do, with the differences being in where > they're built (CentOS community infrastructure vs Red Hat's certified > infrastructure) and the lack of commercial support from Red Hat for > the community versions. > > The main thing changing with the move to using cbs.centos.org is that > there's now a clear upstream home for the softwarecollections.org > build process, rather than the relatively ad hoc approach that needed > to be adopted after Fedora's Engineering Steering Council rejected the > use of Fedora's infrastructure for that purpose. > > Regards, > Nick. > From rcollet at redhat.com Tue Nov 17 08:09:59 2015 From: rcollet at redhat.com (Remi Collet) Date: Tue, 17 Nov 2015 09:09:59 +0100 Subject: [scl.org] SCL for Fedora 23 and SELinux Message-ID: <564AE0D7.5050506@redhat.com> Just FYI, minor change needed if you build a SCL for Fedora 23 In the metapackage: -Requires(post): policycoreutils-python libselinux-utils +Requires(post): %{_root_sbindir}/semanage +Requires(post): %{_root_sbindir}/selinuxenabled Explanation: policycoreutils-python pull python2, which is very probably not what we want., and commands are moved to policycoreutils-python-tools (new package not available in older distro) 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 Thu Nov 19 08:25:33 2015 From: dominic at cleal.org (Dominic Cleal) Date: Thu, 19 Nov 2015 08:25:33 +0000 Subject: [scl.org] Ruby on Rails 4.2 collection Message-ID: <564D877D.50405@cleal.org> Hi folks, I work on the Foreman project (http://theforeman.org) which is a heavy user of the RoR collections on EL6 and EL7. We currently use ruby193, and are migrating to rh-ror41 & rh-ruby22 as I write this. I'm interested in updating to Rails 4.2 soon for parity with Fedora 22+, so I plan to start a new ror42 collection. I'd like to propose this for inclusion under the CentOS SCLo SIG, so it'd be named "sclo-ror42". It would pretty much be a rebuild of Rails 4.2.4 (or .5, released last week) from Fedora 23/rawhide. It would depend on rh-ruby22, and be very similar to rh-ror41. I discussed the idea with Honza at the SCLo sync-up yesterday, who mentioned that RHSCL may decide to ship a similar collection, but not for some time. This sclo-ror42 collection would act as a stop-gap until that's available. Any feedback or offers of help are welcome. Cheers, -- Dominic Cleal dominic at cleal.org From gscrivan at redhat.com Thu Nov 19 11:08:21 2015 From: gscrivan at redhat.com (Giuseppe Scrivano) Date: Thu, 19 Nov 2015 12:08:21 +0100 Subject: [scl.org] Plans for working on an OSTree 2014.09 software collection Message-ID: <87wpte6yca.fsf@foo.bar.baz> Hi, I am working on an OSTree backport to Centos 6 and I am using a Software Collection for doing it. The dependencies needed by OSTree are: glib2, glib-networking, gobject-introspection, gpgme, libassuan, libgpg-error, libgsystem, libproxy, libsoup, ostree, pth, xz. I would like to build this Software Collection on cbs.centos.org, I've already send a request to get access to it: https://bugs.centos.org/view.php?id=9784 Thanks, Giuseppe From ncoghlan at redhat.com Fri Nov 20 05:05:35 2015 From: ncoghlan at redhat.com (Nick Coghlan) Date: Fri, 20 Nov 2015 15:05:35 +1000 Subject: [scl.org] Plans for HTTPS verification in Python 2.7 SCL? Message-ID: With RHEL 7.2 going GA, and CentOS 7.201511 presumably not far behind, is there a public plan for incorporating the Python 2.7 SSL upgrades into the Python 2.7 software collection? Might it make sense to create a sclo-py2710 collection that rebased Python, pip, etc? Regards, Nick. -- Nick Coghlan Fedora Environments & Stacks Red Hat Developer Experience, Brisbane Software Development Workflow Designer & Process Architect From hhorak at redhat.com Fri Nov 20 08:30:19 2015 From: hhorak at redhat.com (Honza Horak) Date: Fri, 20 Nov 2015 09:30:19 +0100 Subject: [scl.org] Plans for HTTPS verification in Python 2.7 SCL? In-Reply-To: References: Message-ID: <564EDA1B.3030507@redhat.com> Do I understand correctly that you're speaking about updating to newer versions than what we have in RHSCL? Honza On 11/20/2015 06:05 AM, Nick Coghlan wrote: > With RHEL 7.2 going GA, and CentOS 7.201511 presumably not far behind, > is there a public plan for incorporating the Python 2.7 SSL upgrades > into the Python 2.7 software collection? > > Might it make sense to create a sclo-py2710 collection that rebased > Python, pip, etc? > > Regards, > Nick. > From ncoghlan at redhat.com Fri Nov 20 14:21:14 2015 From: ncoghlan at redhat.com (Nick Coghlan) Date: Sat, 21 Nov 2015 00:21:14 +1000 Subject: [scl.org] Plans for HTTPS verification in Python 2.7 SCL? In-Reply-To: <564EDA1B.3030507@redhat.com> References: <564EDA1B.3030507@redhat.com> Message-ID: On Fri, Nov 20, 2015 at 6:30 PM, Honza Horak wrote: > Do I understand correctly that you're speaking about updating to newer > versions than what we have in RHSCL? Yes, although I assume any newer version would eventually also make an appearance in RHSCL. The specific point that prompted my question is the Python certificate verification knowledge base article posted along with the RHEL 7.2 release that notes that the python27 and python33 software collections don't currently implement PEPs 476 or 493: https://access.redhat.com/articles/2039753 For the python33 SCL, the PEP 493 supported upgrade path is "upgrade to Python 3.4 if you want certificate verification by default, otherwise stay on Python 3.3 for the time being". For the python27 SCL, that isn't the case - it either needs the same backport as landed in the RHEL 7.2 system Python, or else a rebased software collection that includes the upstream backwards compatibility break. The reason I suggested the idea of a new parallel installable collection that rebased all the included components is that it isn't just CPython that has undergone some backwards incompatible changes, but some of the packaging tools have also received significant changes that pose backwards compatibility concerns. Regards, Nick. -- Nick Coghlan Fedora Environments & Stacks Red Hat Developer Experience, Brisbane Software Development Workflow Designer & Process Architect From hhorak at redhat.com Mon Nov 23 07:02:33 2015 From: hhorak at redhat.com (Honza Horak) Date: Mon, 23 Nov 2015 08:02:33 +0100 Subject: [scl.org] How we've fixed upgrade path for CentOS 6 Software Collections Message-ID: <5652BA09.6060509@redhat.com> Short meesage for those who don't have time: Software Collections builds for CentOS 6 will be soon ready for smooth upgrade from older rebuilds. Now full story for those who care: Shortly after first RHSCL 1.0 release, CentOS rebuilds were prepared and since then they are available under: http://mirror.centos.org/centos/6/SCL/x86_64/ However, keeping these rebuilds in sync with RHSCL content hasn't been easy task. With introduction of Java packages in collections, this task became even more tricky, which means these collections were not updated for long time. With that said, someone would expect there won't be problem with upgrade path, in other words that the new RPMs, that the SCLo SIG group is about to release, will update the older RPMs smoothly. Well, not always. The original RPMs used ".el6.centos.alt" as %dist tag, while new builds use just ".el6" and that evolves in cases where python27-python-bson-2.5.2-4.el6.centos.alt.x86_64 > python27-python-bson-2.5.2-4.el6.x86_64, even if those packages have same Release tag in RPM SPEC. That obviously means the packages won't update smoothly. Solution is quite simple in this case -- use higher Release in RPM SPEC. In some packages, this was already done, because some of the packages received update since original inclusion. In other cases we solve it by adding ".scX" (X is number) suffix to the Release tag. The ".scX" was chosen deliberately since ".scX.el6" is higher (alphabetically) than .el6. Btw. for cases we need to build package more times before final build (bootstraping), we use suffix ".bsX", which means we can build package without any Release suffix in the end, because ".bsX.el6" < ".el6". Anyway, this whole mail was meant to let you know that upgrading of el6 packages from originally built RPMs is something we care about. To verify it works, I've installed all the packages from original repository, then ran "yum update" and that evolved in proper update of all packages. I took that as proof it should work fine in your case as well. If there are still some issues, let us know. This story was also shared at http://www.themindiseverything.eu/2015/11/how-weve-fixed-upgrade-path-for-centos.html. Honza SCLo SIG member From rkratky at redhat.com Mon Nov 23 16:41:49 2015 From: rkratky at redhat.com (Robert Kratky) Date: Mon, 23 Nov 2015 17:41:49 +0100 Subject: [scl.org] Announcing release for Vagrant 1.7.4 on CentOS Linux 7 x86_64 SCL Message-ID: <30817203.9pMzB8erLz@x230> On 11.?11.?2015 17:43:22, Honza Horak wrote: > I am pleased to announce the immediate availability of Vagrant 1.7.4 on > CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by > the SCLo Special Interest Group > (https://wiki.centos.org/SpecialInterestGroup/SCLo). > > QuickStart > ---------- > > You can get started in three easy steps: > $ sudo yum install centos-release-scl > $ sudo yum install sclo-vagrant1 > $ scl enable sclo-vagrant1 bash > > At this point you should be able to use vagrant just as a normal > > application. An example work-flow might be: > $ vagrant init centos/7 > $ vagrant up > $ vagrant ssh > > In order to view the individual components included in this > > collection, including additional vagrant plugins, you can run : > $ sudo yum list sclo-vagrant\* > > Enjoy! > > Honza > SCLo SIG member Hi, I'm looking for an elegant way to document the installation of this collection on RHEL -- without disabling GPG checking. * I don't want to advise users to install the 'centos-release-scl' package, which contains the key for the 'sclo' repo, because it depends on the 'centos-release-scl-rh' package, which enables the repo with SCLs based on the official RHSCL (and I want to pull these from the official RH repo, not from the CentOS repo). * The SCL GPG key isn't included in the 'centos-release' package. * I suppose I could instruct users to download the 'centos-release-scl' package, extract the key, and use 'rpm' to import it to /etc/pki/rpm-gpg/ -- but that seems like a very clutchy solution. Any suggestions? Thanks. Regards, Robert From mail-lists at karan.org Tue Nov 24 00:22:56 2015 From: mail-lists at karan.org (Karanbir Singh) Date: Tue, 24 Nov 2015 00:22:56 +0000 Subject: [scl.org] Announcing release for Vagrant 1.7.4 on CentOS Linux 7 x86_64 SCL In-Reply-To: <30817203.9pMzB8erLz@x230> References: <30817203.9pMzB8erLz@x230> Message-ID: <5653ADE0.7080203@karan.org> On 23/11/15 16:41, Robert Kratky wrote: > On 11.?11.?2015 17:43:22, Honza Horak wrote: > >> I am pleased to announce the immediate availability of Vagrant 1.7.4 on >> CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by >> the SCLo Special Interest Group >> (https://wiki.centos.org/SpecialInterestGroup/SCLo). >> >> QuickStart >> ---------- >> >> You can get started in three easy steps: >> $ sudo yum install centos-release-scl >> $ sudo yum install sclo-vagrant1 >> $ scl enable sclo-vagrant1 bash >> >> At this point you should be able to use vagrant just as a normal >> >> application. An example work-flow might be: >> $ vagrant init centos/7 >> $ vagrant up >> $ vagrant ssh >> >> In order to view the individual components included in this >> >> collection, including additional vagrant plugins, you can run : >> $ sudo yum list sclo-vagrant\* >> >> Enjoy! >> >> Honza >> SCLo SIG member > > Hi, > > I'm looking for an elegant way to document the installation of this collection on RHEL -- without disabling GPG checking. > > * I don't want to advise users to install the 'centos-release-scl' package, which contains the key for the 'sclo' repo, because it depends on the 'centos-release-scl-rh' package, which enables the repo with SCLs based on the official RHSCL (and I want to pull these from the official RH repo, not from the CentOS repo). > > * The SCL GPG key isn't included in the 'centos-release' package. > > * I suppose I could instruct users to download the 'centos-release-scl' package, extract the key, and use 'rpm' to import it to /etc/pki/rpm-gpg/ -- but that seems like a very clutchy solution. > > Any suggestions? if the centos-release-scl-rh were to have a Provides: that matches something that's also available from the RHSCL's setup, then this might not be a problem; in an environ that has the RHSCL's setup, the content will just come from there ( it will need some tracking etc, but should'nt be too hard ). is there such an easy target that might be shared across the two venues ? -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc From hhorak at redhat.com Tue Nov 24 12:15:21 2015 From: hhorak at redhat.com (Honza Horak) Date: Tue, 24 Nov 2015 13:15:21 +0100 Subject: [scl.org] CentOS SCLo SIG sync-up meeting on #centos-devel (2015-11-25) Message-ID: <565454D9.1070903@redhat.com> SCLo SIG meeting will be at 16:00 UTC (11:00 EST, 17:00 Brno, 11:00 Boston, 0:00+1d Tokyo, 1:00+1d Brisbane) in #centos-devel on Freenode. = Topics = * devtoolset-4 rebuilding issues * rh-nginx18 and rh-varnish4 SCL settings * dist-git repos creation -- updates? * review new-SIG-member process (make approval part more concrete) Honza From hhorak at redhat.com Tue Nov 24 12:51:01 2015 From: hhorak at redhat.com (Honza Horak) Date: Tue, 24 Nov 2015 13:51:01 +0100 Subject: [scl.org] Announcing release for Vagrant 1.7.4 on CentOS Linux 7 x86_64 SCL In-Reply-To: <5653ADE0.7080203@karan.org> References: <30817203.9pMzB8erLz@x230> <5653ADE0.7080203@karan.org> Message-ID: <56545D35.80107@redhat.com> On 11/24/2015 01:22 AM, Karanbir Singh wrote: > On 23/11/15 16:41, Robert Kratky wrote: >> On 11.?11.?2015 17:43:22, Honza Horak wrote: >> >>> I am pleased to announce the immediate availability of Vagrant 1.7.4 on >>> CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by >>> the SCLo Special Interest Group >>> (https://wiki.centos.org/SpecialInterestGroup/SCLo). >>> >>> QuickStart >>> ---------- >>> >>> You can get started in three easy steps: >>> $ sudo yum install centos-release-scl >>> $ sudo yum install sclo-vagrant1 >>> $ scl enable sclo-vagrant1 bash >>> >>> At this point you should be able to use vagrant just as a normal >>> >>> application. An example work-flow might be: >>> $ vagrant init centos/7 >>> $ vagrant up >>> $ vagrant ssh >>> >>> In order to view the individual components included in this >>> >>> collection, including additional vagrant plugins, you can run : >>> $ sudo yum list sclo-vagrant\* >>> >>> Enjoy! >>> >>> Honza >>> SCLo SIG member >> >> Hi, >> >> I'm looking for an elegant way to document the installation of this collection on RHEL -- without disabling GPG checking. >> >> * I don't want to advise users to install the 'centos-release-scl' package, which contains the key for the 'sclo' repo, because it depends on the 'centos-release-scl-rh' package, which enables the repo with SCLs based on the official RHSCL (and I want to pull these from the official RH repo, not from the CentOS repo). >> >> * The SCL GPG key isn't included in the 'centos-release' package. >> >> * I suppose I could instruct users to download the 'centos-release-scl' package, extract the key, and use 'rpm' to import it to /etc/pki/rpm-gpg/ -- but that seems like a very clutchy solution. >> >> Any suggestions? > > if the centos-release-scl-rh were to have a Provides: that matches > something that's also available from the RHSCL's setup, then this might > not be a problem; in an environ that has the RHSCL's setup, the content > will just come from there ( it will need some tracking etc, but > should'nt be too hard ). > > is there such an easy target that might be shared across the two venues ? This is not that easy, because RH packages don't use an RPM package for shipping repo file and key -- and there is probably no similar RPM that we could use. We can either create a separate a new RPM package with just sclo repo file and key or as already proposed before, something like this: * centos-release-scl-rh as now, no difference here * centos-release-scl-sclo, that ships repo file and key * centos-release-scl that requires both of the images above, but doesn't ship anything. In case the key won't change often (which I don't expect), we can also have a package build in copr and available on softwarecollections.org if something like the above would be bad idea. Honza From dominic at cleal.org Fri Nov 27 09:42:01 2015 From: dominic at cleal.org (Dominic Cleal) Date: Fri, 27 Nov 2015 09:42:01 +0000 Subject: [scl.org] CentOS SCLo SIG sync-up meeting on #centos-devel (2015-11-25) In-Reply-To: <565454D9.1070903@redhat.com> References: <565454D9.1070903@redhat.com> Message-ID: <56582569.2050309@cleal.org> On 24/11/15 12:15, Honza Horak wrote: > * review new-SIG-member process (make approval part more concrete) I don't think this was discussed in the end, but how would I become a member at the moment? As per https://www.redhat.com/archives/sclorg/2015-November/msg00021.html I'm interested in creating a new SCL under the SIG. Initially I'd like to start by creating a wiki page to plan it under https://wiki.centos.org/SpecialInterestGroup/SCLo, which I don't have permissions to do, and would assume I need to be a member before I'd get edit access to that part of the wiki. It'll be a little while before I'm interested in building in CBS, but I'll also raise bugs for access and to create tags which appears to need SIG membership. Cheers, -- Dominic Cleal dominic at cleal.org From Jaroslaw.Polok at cern.ch Mon Nov 30 09:48:49 2015 From: Jaroslaw.Polok at cern.ch (Jarek Polok) Date: Mon, 30 Nov 2015 10:48:49 +0100 Subject: [scl.org] scl's release ? In-Reply-To: <563C9B77.4010701@redhat.com> References: <5632326B.6070905@cern.ch> <563C9B77.4010701@redhat.com> Message-ID: <565C1B81.5030803@cern.ch> Hello again ! On 11/06/2015 01:22 PM, Honza Horak wrote: [...] > > The collections that we already tested are available already at: > http://mirror.centos.org/centos-7/7/sclo/x86_64/rh/ I see that most of the collections have been uploaded there, however following two are missing: rh-java-common maven30 (I think both have not been tagged as 'release' in cbs ?) The problem with missing rh-java-common is that it is the dependency of: devtoolset-3 (eclipse) rh-mongodb26 thermostat1 collections (which are already there) .. Thanks for looking .. Best Regards Jarek __ ------------------------------------------------------- _ Jaroslaw_Polok __________________ CERN - IT/OIS/WLS _ _ http://cern.ch/~jpolok ________ tel_+41_22_767_1834 _ ______________________________________+41_75_411_9487 _ From rkratky at redhat.com Mon Nov 30 15:47:43 2015 From: rkratky at redhat.com (Robert Kratky) Date: Mon, 30 Nov 2015 16:47:43 +0100 Subject: [scl.org] Announcing release for Vagrant 1.7.4 on CentOS Linux 7 x86_64 SCL In-Reply-To: <56545D35.80107@redhat.com> References: <30817203.9pMzB8erLz@x230> <5653ADE0.7080203@karan.org> <56545D35.80107@redhat.com> Message-ID: <1448902355.MyhgHxboyd@x230> On 24.?11.?2015 13:51:01, Honza Horak wrote: > On 11/24/2015 01:22 AM, Karanbir Singh wrote: > > On 23/11/15 16:41, Robert Kratky wrote: > >> On 11.?11.?2015 17:43:22, Honza Horak wrote: > >> > >>> I am pleased to announce the immediate availability of Vagrant 1.7.4 on > >>> CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by > >>> the SCLo Special Interest Group > >>> (https://wiki.centos.org/SpecialInterestGroup/SCLo). > >>> > >>> QuickStart > >>> ---------- > >>> > >>> You can get started in three easy steps: > >>> $ sudo yum install centos-release-scl > >>> $ sudo yum install sclo-vagrant1 > >>> $ scl enable sclo-vagrant1 bash > >>> > >>> At this point you should be able to use vagrant just as a normal > >>> > >>> application. An example work-flow might be: > >>> $ vagrant init centos/7 > >>> $ vagrant up > >>> $ vagrant ssh > >>> > >>> In order to view the individual components included in this > >>> > >>> collection, including additional vagrant plugins, you can run : > >>> $ sudo yum list sclo-vagrant\* > >>> > >>> Enjoy! > >>> > >>> Honza > >>> SCLo SIG member > >> > >> Hi, > >> > >> I'm looking for an elegant way to document the installation of this collection on RHEL -- without disabling GPG checking. > >> > >> * I don't want to advise users to install the 'centos-release-scl' package, which contains the key for the 'sclo' repo, because it depends on the 'centos-release-scl-rh' package, which enables the repo with SCLs based on the official RHSCL (and I want to pull these from the official RH repo, not from the CentOS repo). > >> > >> * The SCL GPG key isn't included in the 'centos-release' package. > >> > >> * I suppose I could instruct users to download the 'centos-release-scl' package, extract the key, and use 'rpm' to import it to /etc/pki/rpm-gpg/ -- but that seems like a very clutchy solution. > >> > >> Any suggestions? > > > > if the centos-release-scl-rh were to have a Provides: that matches > > something that's also available from the RHSCL's setup, then this might > > not be a problem; in an environ that has the RHSCL's setup, the content > > will just come from there ( it will need some tracking etc, but > > should'nt be too hard ). > > > > is there such an easy target that might be shared across the two venues ? > > This is not that easy, because RH packages don't use an RPM package for > shipping repo file and key -- and there is probably no similar RPM that > we could use. > > We can either create a separate a new RPM package with just sclo repo > file and key or as already proposed before, something like this: > * centos-release-scl-rh as now, no difference here > * centos-release-scl-sclo, that ships repo file and key > * centos-release-scl that requires both of the images above, but doesn't > ship anything. Either of these solutions seems good to me. Would it be hard to make it happen? Regards, Robert > In case the key won't change often (which I don't expect), we can also > have a package build in copr and available on softwarecollections.org if > something like the above would be bad idea. > > Honza From rkratky at redhat.com Mon Nov 30 17:10:34 2015 From: rkratky at redhat.com (Robert Kratky) Date: Mon, 30 Nov 2015 18:10:34 +0100 Subject: [scl.org] Announcing release for Vagrant 1.7.4 on CentOS Linux 7 x86_64 SCL Message-ID: <2811844.Wi5Qto1cL8@x230> On 11.?11.?2015 17:43:22, Honza Horak wrote: > I am pleased to announce the immediate availability of Vagrant 1.7.4 on > CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by > the SCLo Special Interest Group > (https://wiki.centos.org/SpecialInterestGroup/SCLo). > > QuickStart > ---------- > > You can get started in three easy steps: > $ sudo yum install centos-release-scl > $ sudo yum install sclo-vagrant1 > $ scl enable sclo-vagrant1 bash > > At this point you should be able to use vagrant just as a normal > > application. An example work-flow might be: > $ vagrant init centos/7 > $ vagrant up > $ vagrant ssh > > In order to view the individual components included in this > > collection, including additional vagrant plugins, you can run : > $ sudo yum list sclo-vagrant\* > > Enjoy! > > Honza > SCLo SIG member Hi, Will the package with the 'vagrant-registration' plugin [1] be released asynchronously with the 1.0.0 version of the plugin, or is it only going to happen with the next release of Vagrant? Also, are there plans to package the 'vagrant-adbinfo' plugin [2]? Thanks. Regards, Robert [1] sclo-vagrant1-vagrant-registration-0.0.19-5.el7.noarch.rpm [2] https://github.com/projectatomic/vagrant-adbinfo From jstribny at redhat.com Mon Nov 30 22:49:06 2015 From: jstribny at redhat.com (Josef Stribny) Date: Mon, 30 Nov 2015 23:49:06 +0100 Subject: [scl.org] Announcing release for Vagrant 1.7.4 on CentOS Linux 7 x86_64 SCL In-Reply-To: <2811844.Wi5Qto1cL8@x230> References: <2811844.Wi5Qto1cL8@x230> Message-ID: <1448923746.13272.0@smtp.corp.redhat.com> Hi, yes update to the new version is planned. I will be merging two new features hopefully and then both Fedora and this SCL get updates. I can include vagrant-adbinfo plugin as well. Best Josef On Mon, Nov 30, 2015 at 6:10 PM, Robert Kratky wrote: > On 11.?11.?2015 17:43:22, Honza Horak wrote: > >> I am pleased to announce the immediate availability of Vagrant >> 1.7.4 on >> CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) >> built by >> the SCLo Special Interest Group >> (https://wiki.centos.org/SpecialInterestGroup/SCLo). >> >> QuickStart >> ---------- >> >> You can get started in three easy steps: >> $ sudo yum install centos-release-scl >> $ sudo yum install sclo-vagrant1 >> $ scl enable sclo-vagrant1 bash >> >> At this point you should be able to use vagrant just as a normal >> >> application. An example work-flow might be: >> $ vagrant init centos/7 >> $ vagrant up >> $ vagrant ssh >> >> In order to view the individual components included in this >> >> collection, including additional vagrant plugins, you can run : >> $ sudo yum list sclo-vagrant\* >> >> Enjoy! >> >> Honza >> SCLo SIG member > > Hi, > > Will the package with the 'vagrant-registration' plugin [1] be > released asynchronously with the 1.0.0 version of the plugin, or is > it only going to happen with the next release of Vagrant? > > Also, are there plans to package the 'vagrant-adbinfo' plugin [2]? > > Thanks. > > Regards, > Robert > > [1] sclo-vagrant1-vagrant-registration-0.0.19-5.el7.noarch.rpm > [2] https://github.com/projectatomic/vagrant-adbinfo > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg -------------- next part -------------- An HTML attachment was scrubbed... URL: