From hhorak at redhat.com Wed Aug 5 14:40:19 2015 From: hhorak at redhat.com (Honza Horak) Date: Wed, 05 Aug 2015 16:40:19 +0200 Subject: [scl.org] CentOS SCLo SIG sync-up meeting on #centos-devel (2015-08-05) Message-ID: <55C22053.2040905@redhat.com> SCLo SIG meeting will be at 15: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 = * dist-git repos -- do we want to create all at once? * vagrant SCL as example of sclo upstream collection (sorry for late announcement) Honza From hhorak at redhat.com Wed Aug 5 16:25:22 2015 From: hhorak at redhat.com (Honza Horak) Date: Wed, 05 Aug 2015 18:25:22 +0200 Subject: [scl.org] Log from CentOS SCLo SIG sync-up meeting on #centos-devel (2015-08-05) In-Reply-To: <55C22053.2040905@redhat.com> References: <55C22053.2040905@redhat.com> Message-ID: <55C238F2.90409@redhat.com> (05:06:27 PM) hhorak: #startmeeting SCLo SIG sync-up (2015-08-05) (05:06:27 PM) centbot: Meeting started Wed Aug 5 15:06:26 2015 UTC. The chair is hhorak. Information about MeetBot at http://wiki.debian.org/MeetBot. (05:06:27 PM) centbot: Useful Commands: #action #agreed #help #info #idea #link #topic. (05:06:31 PM) hhorak: #meetingname sclo-sig-syncup (05:06:31 PM) centbot: The meeting name has been set to 'sclo-sig-syncup' (05:07:10 PM) The account has disconnected and you are no longer in this chat. You will automatically rejoin the chat when the account reconnects. (05:08:03 PM) The topic for #centos-devel is: CentOS Developers and Contributors room | If you have questions regarding CentOS please see #centos (05:08:03 PM) Topic for #centos-devel set by z00dax!~kbsingh at chakra.karan.org at 09:26:30 AM on 12/11/2012 (05:08:08 PM) The account has disconnected and you are no longer in this chat. You will automatically rejoin the chat when the account reconnects. (05:08:45 PM) The topic for #centos-devel is: CentOS Developers and Contributors room | If you have questions regarding CentOS please see #centos (05:08:45 PM) Topic for #centos-devel set by z00dax!~kbsingh at chakra.karan.org at 09:26:30 AM on 12/11/2012 (05:09:08 PM) hhorak1: hm, I lost connection shortly after starting the meeting, so might miss if anybody already waived :) (05:10:00 PM) ***langdon lurks (05:10:06 PM) DV [~veillard at 2001:41d0:1:d478::1] entered the room. (05:10:19 PM) ***lalatenduM _o/ (05:10:23 PM) alphacc: hhorak: o/ (05:10:30 PM) jstribny: hi (05:10:41 PM) bstinson: -_o_- (05:10:53 PM) hhorak1: langdon: great you're here :) I've added the prefix thing on the agenda... :) so let's start with the whole vagrant thing... (05:10:59 PM) hhorak left the room (quit: Ping timeout: 252 seconds). (05:11:04 PM) You are now known as hhorak (05:11:10 PM) jstribny: yes please (05:11:16 PM) lalatenduM: :) (05:11:39 PM) langdon: hhorak, you already know what I am gonna say :) (05:11:48 PM) jstribny: so we need to build rh-ruby22 and rh-ror41 and then sclo-vagrant1 (05:12:06 PM) langdon: jstribny, we should already have the ruby and ror, no? (05:12:12 PM) jstribny: where? (05:12:15 PM) ***langdon means "in cent scl sig" (05:12:39 PM) hhorak: So, we want vagrant in centos and since we're gonna build rh-ruby22 and rh-ror41 collections there, it makes sense having vagrant as SCL as well in centos (comparing to normal RPM) (05:12:59 PM) hhorak: langdon: we have it only in copr, same as other scls lalatenduM Lalufu langdon larsks lars_kurth (05:13:20 PM) langdon: hhorak, ohh.. sorry.. i thought they had come over already.. i get my dates confused some times :) (05:13:26 PM) hhorak: langdon: but the plan is to build all the collections and keep their source in centos, so other centos projects can use it (05:13:34 PM) langdon: hhorak, +1 (05:13:44 PM) langdon: with links from scl.o would be nice too (05:14:17 PM) hhorak: langdon: right, that's also on the todo list, just a bit more down :) (05:14:17 PM) lalatenduM: hhorak: +1 (05:15:20 PM) jstribny: is there some semi-automatic rebuild of scls planned? (05:15:26 PM) jstribny: i mean like the copr one (05:15:42 PM) dougsland [~dougsland at tchelinux/moderator/dougsland] entered the room. (05:16:54 PM) hhorak: jstribny: yes, we have already the packages from scl.org imporeted into cbs.koji.org, so we shouldn't have issues with bootstrapping.. and should be able to do the builds almost automatically (05:17:01 PM) hhorak: (hopefully fully automatically) (05:17:41 PM) alaird [~alan at 74.121.28.6] entered the room. (05:17:46 PM) hhorak: so, since vagrant is not the rh collection, it will be the first collection as upstream only -- that means it will not use rh- prefix.. but which prefix then? have we already discuss this? (05:17:56 PM) hhorak: sclo- seems like one option... (05:18:32 PM) jstribny: hhorak, i dont really like prefixes at all to be honest:) (05:19:14 PM) hhorak: jstribny: yeah, you're not alone, that's what we have langdon, who can nicely explain why they are no evil (05:19:15 PM) hhorak: :) (05:19:38 PM) hhorak: #link https://www.redhat.com/archives/sclorg/2015-February/msg00022.html (05:19:49 PM) hhorak: (just if anybody wonders which prefixes we talk about) (05:20:41 PM) langdon: sorry.. was talking in my other call (05:21:08 PM) hhorak: from my PoV we simply need them to distinguish vagrant SCL that includes all plugins available in the world (e.g. build in centos upstream) and vagrant with only some necessary plugins available in RH once... (05:21:54 PM) nshaikh [nshaikh at nat/redhat/x-gojnfqdoasqifhss] entered the room. (05:22:03 PM) langdon: so.. in short .. the "rh-" prefix indicates that "red hat peopl decided that these are the right things to put in to a vagrant collection" .. vs "cox- = company x decided these are the right things to put in the vagrant collection" (05:22:08 PM) hhorak: This issue is more relevant in python collections where also, modules are either available or not... so the set of plugins/modules kind of defines what the software collections provides.. (05:22:59 PM) jstribny: i see, but then we should stick with rh- (05:23:01 PM) langdon: it does not (necessarily) imply that rht supports it, endorses it, etc.. (05:23:16 PM) hhorak: another reason is to avoid conflicts we already saw (mysql55 package and mysql55 SCL -- both rpms, but every contains something different) (05:23:31 PM) langdon: it could as easily be jstribny- (except you need a shorter name and a llanal registration ;) ) (05:23:36 PM) masta left the room (quit: Ping timeout: 244 seconds). (05:24:29 PM) lars_kurth left the room (quit: Remote host closed the connection). (05:24:53 PM) lars_kurth [~lars_kurt at 97e55056.skybroadband.com] entered the room. (05:25:08 PM) hhorak: langdon: wait, do we need register sclo-? that's just part of the name for the collection... (05:25:51 PM) jstribny: langdon, hhorak well i dont think vagrant1 would conflict with anything in centos (as opposed to other possible scls in future) (05:26:10 PM) alphacc: to not confuse (more) people I'll stick to rh/sclo at this time :) (05:26:18 PM) langdon: hhorak, technically, we are supposed to.. that was the rule.. (and it would be just sclo, but i figure you meant that).. but... i get shaky on sclo- prefix because it implies that it is the canonical scl for that scl.. which is not necessarily a good implication (05:27:04 PM) ***lalatenduM is already confused :-) (05:27:07 PM) jstribny: i am personally inclined to use rh-vagrant1 (05:27:17 PM) langdon: jstribny, the point is not if it conflicts now.. it is if it conflicts in the future or if someone is doing a "secret" one now that they want to push to public later (05:27:46 PM) ***lalatenduM prefers centos inplace of rh. not sure if it makes sense (05:28:37 PM) jstribny: langdon, i know but then again if someone do unprefixed scl.....why that someone should not be us? :)) (05:28:54 PM) hhorak: jstribny: I'm afraid that rh-vagrant1 would imply we need to ship/support all the plugins in rhscl (once vagrant is becoming part of that, if at all) that we have in centos (05:29:13 PM) langdon: jstribny, no un-prefixed scls.. is the recommendation (05:29:32 PM) langdon: hhorak, i disagree but understand your point.. (05:29:45 PM) langdon: half-kidding, epel-vagrant1 ? (05:29:59 PM) hhorak: langdon: now even I am confused :) (05:30:00 PM) langdon: or rh-epel-vagrant1 (05:30:37 PM) jstribny: hhorak, sclo should be always used for upstream? (05:30:38 PM) hhorak: I think we need some generic prefix usable also for collections that will never ever have anything common with rh (05:30:49 PM) langdon: i don't think an rh- prefix should ever indicate that it will be in rhscl.. just that rht employees were the leads on its definition.. but I understand why that may not be obvious to everyone (05:30:51 PM) hhorak: jstribny: that was how I meant it (05:31:05 PM) jstribny: then i believe this would be upsteam (05:31:12 PM) langdon: hhorak, that is why i like something like epel- ... (05:31:23 PM) ***RemiFedora uses "more" (e.g. more-php56) for packages extending "rh" SCL (rh-php56) redkilian reetspissedoff reLad RemiFedora (05:32:03 PM) DV left the room (quit: Remote host closed the connection). (05:32:04 PM) langdon: just the problem is it *isn't* upstream.. it is just one option.. it is not the *only* rpm-scl-ified vagrant collection.. as it would be if it was a "real" rpm.. (05:32:06 PM) dcaro is now known as dcaro_mtg (05:32:06 PM) hhorak: RemiFedora: that's also something we should do the same.. (05:32:18 PM) hhorak: (in other similar extending collections) (05:33:18 PM) ***hhorak wondering whether kbsingh is round, he's always liked the prefix discussion :) (05:33:22 PM) alphacc: I think we did agreed in term of sclo rebuild starting with rh- should be what is shipped by redhat scls. same relation centos <-> rhel. (05:33:22 PM) langdon: RemiFedora "should" be using something like rh-php56-more though.. because it is *still* based on the "rht defined idea of the php collection" (05:33:39 PM) jstribny: langdon, but that implies there is never upstream (05:33:45 PM) langdon: jstribny, exactly (05:33:59 PM) RemiFedora: langdon, your wrong, rh-php56 take upstream from "remi" repo ;) (05:34:36 PM) langdon: RemiFedora, ohh.. i was thinking of your "extra packages" that are not in rhscl.. (05:35:07 PM) RemiFedora: langdon, in "remi" you have eveything, then "rh" pull some, and the others go to "more" (05:35:14 PM) jstribny: langdon, but i create vagrant1, i made the project, i am upstream....you can still do my-own-vagrant-scl as alternative vagrant collection..... (05:35:17 PM) langdon: i think RemiFedora's version should just be called rh-php56 which is the upstream of rh-php56 productized in rhscl (if that is what it is) (05:35:43 PM) langdon: jstribny, right.. hence.. you could use jstribny- (05:35:52 PM) RemiFedora: langdon, not possible, I already have p?p70 SCL, I don't know yet if it will go to rh ... (05:36:41 PM) jstribny: langdon, but this would be CentOS official scl so probably not jstribny- (although i would love to be so famous) (05:37:12 PM) langdon: i am not sure why this is so hard to explain.. but.. the short version is.. i think we should be careful to not "claim namespace territory" that we don't intend to claim.. so. i really don't care that much :) and am happy to say "call it whatever" just be aware of the implications being made... (05:37:37 PM) erdic left the room (quit: Ping timeout: 246 seconds). (05:37:39 PM) hhorak: hm, I don't think we should use names in centos, we should find nice identification of the whole group instead (I still like sclo the most) (05:38:16 PM) erdic [~erdic at unaffiliated/motley] entered the room. (05:39:00 PM) jstribny: i am fine with sclo (05:39:24 PM) lars_kurth left the room (quit: Ping timeout: 264 seconds). (05:40:40 PM) avij left the room (quit: Ping timeout: 258 seconds). (05:40:41 PM) avij [~anssi at leopardi.miuku.net] entered the room. (05:40:54 PM) ***langdon abstains :) (05:43:01 PM) hhorak: so, let's move on, I confess I'm biased but sclo seems like least problematic :) (05:43:19 PM) hhorak: so let's go with sclo at least for vagrant... alaird alivigni alphacc ksb kstange (05:45:39 PM) JHogarth left the room (quit: Quit: JHogarth). (05:45:41 PM) hhorak: Another point on the agenda was mainly about https://bugs.centos.org/view.php?id=9151 -- I was going to ask kbsingh whether this ticket is fine or some information is missing.. (05:45:41 PM) hhorak: but since he doesn't seem to be around, alphacc or bstinson -- anybody involved in dist-git repos creating? (05:46:21 PM) hhorak: I was also thinking about creating request for other components from rhscl at once, there's basically no need to wait with that.. (05:46:36 PM) hhorak: so if nobody stops me, I'll do it tomorrow :) (05:47:23 PM) DV [~veillard at 2001:41d0:a:f29f::1] entered the room. (05:47:55 PM) asad_ [~asad_ at c048.fem.tu-ilmenau.de] entered the room. (05:48:30 PM) bstinson: hhorak: are these the final dist-git repos that you need? i.e. the ones that go in the RPMS/ project? (05:48:32 PM) jstribny: please do (05:48:53 PM) jstribny: but for vagrant you probably need a list of components right> (05:49:49 PM) xaeth is now known as xaeth_afk (05:51:26 PM) bstinson: if they're the staging ones you should be able to create those repos under the sclo project yourself (05:51:29 PM) hhorak: bstinson: these should still be under sclo/ project and the plan is still build from srpm.. we can't build from rpms/ (i.e. from scm) until we have lookaside cache working, right? (05:51:38 PM) hhorak: jstribny: yes, can you send me the list, please? (05:52:37 PM) lalatenduM: I would suggest a github organisation as of now till we have the dist git working (05:54:30 PM) lalatenduM: or whatever u guys think is right :) (05:54:44 PM) sbonazzo left the room (quit: Quit: Leaving.). (05:54:56 PM) gamename [~gamename at c-67-177-166-184.hsd1.tn.comcast.net] entered the room. (05:55:00 PM) jstribny: hhorak, http://etherpad.corp.redhat.com/V4kXtF6ixQ (05:55:00 PM) hhorak: bstinson: just tried to create sig-sclo/Judy and received 'your personal repository must be located at "~hhorak"' (05:55:11 PM) hhorak: jstribny: thx (05:55:30 PM) hhorak: bstinson: I must do something wrong (05:55:53 PM) langdon: lalatenduM, https://github.com/sclorg ? (05:56:08 PM) xaeth_afk is now known as xaeth (05:56:18 PM) lalatenduM: langdon: yeah , that sounds fine (05:56:25 PM) langdon: lalatenduM, it exists :) (05:56:48 PM) bstinson: hhorak: ah, something going on with permissions then. that's a kbsingh question (05:57:02 PM) hhorak: bstinson: ok, will ask him (05:58:39 PM) hhorak: lalatenduM: langdon: dist-git should be actually ready, at least the sig-sclo ... so I don't think we must do it (commit sources) twice, once to github, then to git.c.o (05:58:41 PM) oere left the room (quit: Quit: Leaving.). (05:58:57 PM) lalatenduM: hhorak: agree (05:58:59 PM) langdon: hhorak, ack.. i was just answering lalatenduM's q (05:59:15 PM) hhorak: great :) (05:59:33 PM) hhorak: ok, anybody else something to discuss today? (05:59:58 PM) hhorak: (I have some new todo items, so will sleep well :) ) (06:00:06 PM) alphacc: hhorak: drop me the full list of collections when you can. (06:00:24 PM) hhorak: alphacc: just the collections or all the packages as well? (06:00:48 PM) alphacc: hhorak: just the collections that need tags in koji :) (06:01:13 PM) hhorak: alphacc: ok, will do. (06:02:16 PM) hhorak: so, closing in a minute :) (06:02:25 PM) alphacc: hhorak: what's the plan for rhscl 6 rebuild at this time ? (06:02:39 PM) alphacc: (last one and I let you go:) (06:03:25 PM) langdon: hhorak, and, from me, do we have a rough eta on any of this? I use the vagrant scl a fair amount and would like updates :) (06:04:29 PM) alphacc: Becasue we rebuild rhscl at work and if it does not appear soon I'll have to kick off a rebuild ; however I'll prefer to do it part of sclo. (06:05:14 PM) hhorak: alphacc: hm, no plans for now, we said we start the proof of concept builds on rhel-7 only... but the PoC was kind of done and it might be more effective to do it at once right? (06:05:32 PM) jstribny: langdon, once ruby scls are rebuilt and i have access to branches, i could build it in two-three days (06:05:37 PM) alphacc: hhorak: at once meaning when we have dist-git ? (06:06:42 PM) alphacc: hhorak: or we can consider a srpm rebuild to have something quickly ? (06:07:00 PM) shaunm left the room (quit: Ping timeout: 244 seconds). (06:07:03 PM) hhorak: alphacc: I meant building rhel6 builds kind of together with rhel7 ones.. (06:07:10 PM) sayan [~sayan at fedora/sayan] entered the room. (06:08:03 PM) hhorak: alphacc: yeah, I think we can have srpm builds for rhel6 as well, I don't see why we couldn't.. (06:08:29 PM) gsanchietti left the room (quit: Quit: Ex-Chat). (06:08:48 PM) alphacc: hhorak: ok, ping me if it's a matter a sending srpm in correct order I can help. (06:09:27 PM) hhorak: langdon: I'm always too positive about eta, so if I say having vagrant for rhel7 built till end of august.. I may be too positive again.. or might not.. (06:09:50 PM) mdittmeier [~mdittmeie at ip68-108-96-112.lv.lv.cox.net] entered the room. (06:09:57 PM) langdon: hhorak, lol (06:10:10 PM) hhorak: alphacc: if we use the same way (import scl.org packages into cbs), which we probably must anyway... the order should be irrelevant (06:11:03 PM) alphacc: hhorak: if you use the bootstrap repo everywhere (06:12:41 PM) hhorak: alphacc: do you think it is problem? I thought we could use it everywhere to save troubles with bootstrapping and circular dependencies.. these are not scm builds anyway :) (06:15:18 PM) alan_ [~alan at 93-139-204-195.adsl.net.t-com.hr] entered the room. (06:15:41 PM) alan_ is now known as Guest11649 (06:17:16 PM) talori left the room (quit: Quit: Leaving.). (06:18:24 PM) jstribny left the room (quit: Quit: Leaving). (06:18:54 PM) apevec left the room (quit: Ping timeout: 260 seconds). (06:19:37 PM) davidep left the room (quit: Quit: Leaving.). (06:19:53 PM) alphacc: hhorak: not a problem but I'd like to rebuild against what we have at a point (06:20:40 PM) hhorak: alphacc: fine with me, that should be just another round of scripted builds... theoretically :) (06:21:14 PM) alphacc: hhorak: again just my opinion run it thorugh everybody :) (06:21:17 PM) Guest11649 left the room ("Leaving"). (06:21:49 PM) ***alphacc & (06:21:53 PM) alphacc: thanks all (06:22:05 PM) hhorak: so, I'll prepare the list of scl.org repos for rhel6 and we can create one testing rhel6 scl first.. sounds fine? (06:22:14 PM) hhorak: I'll need to leave as well, thanks all !!! (06:23:00 PM) hhorak: #endmeeting (06:23:00 PM) centbot: Meeting ended Wed Aug 5 16:22:59 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) (06:23:00 PM) centbot: Minutes: centos-devel/2015/centos-devel.2015-08-05-15.06.html (06:23:00 PM) centbot: Minutes (text): centos-devel/2015/centos-devel.2015-08-05-15.06.txt (06:23:00 PM) centbot: Log: centos-devel/2015/centos-devel.2015-08-05-15.06.log.html From hhorak at redhat.com Thu Aug 6 15:08:13 2015 From: hhorak at redhat.com (Honza Horak) Date: Thu, 06 Aug 2015 17:08:13 +0200 Subject: [scl.org] rhscl dockerfiles In-Reply-To: References: <55C348C9.8070808@redhat.com> <55C35EBF.9050401@redhat.com> Message-ID: <55C3785D.1070607@redhat.com> Adding Tomas into CC, he maintains nodejs and has better knowledge what it means to run nodejs app. My nodejs-unexperienced thought would be you can create a new docker image, that will use `FROM: nodejs-010-rhel7` and: * add the app code somewhere into the image (e.g. into /opt/app-root/app) * changing CMD to run your application on pure `docker run` Or, theoretically, you don't have to create a new layer (image), just use volume mounting to get your app into the container. It would mean to run the image this way: #> docker run -v /your/app:/opt/app-root/app nodej-010-rhel7 /opt/app-root/app/run.sh But I may be also wrong about how it is the best to do it. Or whether this way is something we should or shouldn't recommend. Sharing also to the ML, maybe others might have different opinions/ideas or at least issues. Honza On 08/06/2015 03:42 PM, David Martin wrote: > If there's a recommended way to use the sti nodejs image for simply > running a node app, that'd be great. > I'll spend some time trying to figure it out as I can't find Usage docs > other than doing an sti build. > > re: Dockerfile.rhel7, > Ah, I didn't spot this at first. Thanks > > On Thu, Aug 6, 2015 at 2:18 PM, Honza Horak > wrote: > > Well, you can, but at least to my understanding you shouldn't need > it. Even if the sti scripts are part of the image, you don't have to > use them if you don't want to. Or do you have a use case where you > cannot use an image with sti scripts? > > btw. if you seek for rhel dockerfile, just look at Dockerfile.rhel7 > in the same directory. > > Honza > > On 08/06/2015 02:05 PM, David Martin wrote: > > Ok, thanks. > > I don't understand why though. Its an STI image, and its centos. > > I guess I can take the original rhel7 nodejs dockerfile and build it > myself to get a non STI image on rhel7. > > On Thu, Aug 6, 2015 at 12:45 PM, Honza Horak > >> wrote: > > On 08/06/2015 01:35 PM, David Martin wrote: > > Hi Honza, > > I'm looking to use the rhel7.nodejs010 dockerfile from > the rhscl > repo > https://github.com/sclorg/rhscl-dockerfiles > however, I see that it was recently removed. > In the removal comment you mentioned "Remove > dockerfiles sources > that > have upstream under https://github.com/openshift/" > Maybe I'm misunderstanding something or missing a part > of the > picture, > but where is the upstream you are referring to? > Is it the STI image based on centos you are referring > to here? > https://github.com/openshift/sti-nodejs/blob/master/0.10/Dockerfile > > > Yes, that one it is. After discussion we decided not to > continue > with the original rhel7.nodejs010 dockerfile and only use > https://github.com/openshift/sti-nodejs/blob/master/0.10/Dockerfile > in RH -- that one is base for official RH image now. > > Honza > > Thanks > > David Martin > > > From thrcka at redhat.com Fri Aug 7 06:38:07 2015 From: thrcka at redhat.com (Tomas Hrcka) Date: Fri, 07 Aug 2015 08:38:07 +0200 Subject: [scl.org] rhscl dockerfiles In-Reply-To: <55C3785D.1070607@redhat.com> References: <55C348C9.8070808@redhat.com> <55C35EBF.9050401@redhat.com> <55C3785D.1070607@redhat.com> Message-ID: <55C4524F.5040803@redhat.com> On 08/06/2015 05:08 PM, Honza Horak wrote: > Adding Tomas into CC, he maintains nodejs and has better knowledge > what it means to run nodejs app. > > My nodejs-unexperienced thought would be you can create a new docker > image, that will use `FROM: nodejs-010-rhel7` and: > * add the app code somewhere into the image (e.g. into /opt/app-root/app) > * changing CMD to run your application on pure `docker run` > > Or, theoretically, you don't have to create a new layer (image), just > use volume mounting to get your app into the container. It would mean > to run the image this way: > > #> docker run -v /your/app:/opt/app-root/app nodej-010-rhel7 > /opt/app-root/app/run.sh > > But I may be also wrong about how it is the best to do it. Or whether > this way is something we should or shouldn't recommend. > > Sharing also to the ML, maybe others might have different > opinions/ideas or at least issues. > > Honza > > On 08/06/2015 03:42 PM, David Martin wrote: >> If there's a recommended way to use the sti nodejs image for simply >> running a node app, that'd be great. >> I'll spend some time trying to figure it out as I can't find Usage docs >> other than doing an sti build. Hi David, what I did when testing sti-nodejs, was that I have build sti-base[1] from scratch for rhel7. You will end up with openshift/base-rhel7 build sti-nodejs afterwards you will have openshift/nodejs-010-rhel7 in you local images list. Now you are ready to build&run your nodejs application image with sti, like explained in usage[3]. [1] - https://github.com/openshift/sti-base [2] - https://github.com/openshift/sti-nodejs [3] - https://github.com/openshift/sti-nodejs/blob/master/0.10/.sti/bin/usage -- Tomas Hrcka Software Engineer - Developer Experience From thrcka at redhat.com Fri Aug 7 10:54:36 2015 From: thrcka at redhat.com (Tomas Hrcka) Date: Fri, 7 Aug 2015 12:54:36 +0200 Subject: [scl.org] rhscl dockerfiles In-Reply-To: References: <55C348C9.8070808@redhat.com> <55C35EBF.9050401@redhat.com> <55C3785D.1070607@redhat.com> <55C4524F.5040803@redhat.com> Message-ID: <55C48E6C.5010900@redhat.com> On 08/07/2015 11:07 AM, David Martin wrote: > Thanks Tomas. > > Maybe my problem wasn't explained clearly enough. Apologies. > > I like to use a base nodejs image that behaves more like the one > available on docker hub https://hub.docker.com/_/node/ > as opposed to one that requires the sti tools. You can use the sti tools just to build the nodejs010 base image. Or pull it from internal registry registry.access.redhat.com/openshift3/nodejs-010-rhel7 > > e.g. I can use a Dockerfile like this to build a container for my app > > ``` > FROM nodejs > ADD . /usr/src/app > ``` and build your app using appropriate tag in FROM > > then do a `docker build` and I have my image for my app. > > > On Fri, Aug 7, 2015 at 7:38 AM, Tomas Hrcka > wrote: > > On 08/06/2015 05:08 PM, Honza Horak wrote: > > Adding Tomas into CC, he maintains nodejs and has better > knowledge what it means to run nodejs app. > > My nodejs-unexperienced thought would be you can create a new > docker image, that will use `FROM: nodejs-010-rhel7` and: > * add the app code somewhere into the image (e.g. into > /opt/app-root/app) > * changing CMD to run your application on pure `docker run` > > Or, theoretically, you don't have to create a new layer > (image), just use volume mounting to get your app into the > container. It would mean to run the image this way: > > #> docker run -v /your/app:/opt/app-root/app nodej-010-rhel7 > /opt/app-root/app/run.sh > > But I may be also wrong about how it is the best to do it. Or > whether this way is something we should or shouldn't recommend. > > Sharing also to the ML, maybe others might have different > opinions/ideas or at least issues. > > Honza > > On 08/06/2015 03:42 PM, David Martin wrote: > > If there's a recommended way to use the sti nodejs image > for simply > running a node app, that'd be great. > I'll spend some time trying to figure it out as I can't > find Usage docs > other than doing an sti build. > > > Hi David, > what I did when testing sti-nodejs, was that I have build > sti-base[1] from scratch for rhel7. You will end up with > openshift/base-rhel7 > build sti-nodejs afterwards you will have > openshift/nodejs-010-rhel7 in you local images list. Now you are > ready to build&run your nodejs application image with sti, like > explained in usage[3]. > > > > > [1] - https://github.com/openshift/sti-base > [2] - https://github.com/openshift/sti-nodejs > [3] - > https://github.com/openshift/sti-nodejs/blob/master/0.10/.sti/bin/usage > > -- > Tomas Hrcka > Software Engineer - Developer Experience > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From davmarti at redhat.com Fri Aug 7 09:07:29 2015 From: davmarti at redhat.com (David Martin) Date: Fri, 7 Aug 2015 10:07:29 +0100 Subject: [scl.org] rhscl dockerfiles In-Reply-To: <55C4524F.5040803@redhat.com> References: <55C348C9.8070808@redhat.com> <55C35EBF.9050401@redhat.com> <55C3785D.1070607@redhat.com> <55C4524F.5040803@redhat.com> Message-ID: Thanks Tomas. Maybe my problem wasn't explained clearly enough. Apologies. I like to use a base nodejs image that behaves more like the one available on docker hub https://hub.docker.com/_/node/ as opposed to one that requires the sti tools. e.g. I can use a Dockerfile like this to build a container for my app ``` FROM nodejs ADD . /usr/src/app ``` then do a `docker build` and I have my image for my app. On Fri, Aug 7, 2015 at 7:38 AM, Tomas Hrcka wrote: > On 08/06/2015 05:08 PM, Honza Horak wrote: > >> Adding Tomas into CC, he maintains nodejs and has better knowledge what >> it means to run nodejs app. >> >> My nodejs-unexperienced thought would be you can create a new docker >> image, that will use `FROM: nodejs-010-rhel7` and: >> * add the app code somewhere into the image (e.g. into /opt/app-root/app) >> * changing CMD to run your application on pure `docker run` >> >> Or, theoretically, you don't have to create a new layer (image), just use >> volume mounting to get your app into the container. It would mean to run >> the image this way: >> >> #> docker run -v /your/app:/opt/app-root/app nodej-010-rhel7 >> /opt/app-root/app/run.sh >> >> But I may be also wrong about how it is the best to do it. Or whether >> this way is something we should or shouldn't recommend. >> >> Sharing also to the ML, maybe others might have different opinions/ideas >> or at least issues. >> >> Honza >> >> On 08/06/2015 03:42 PM, David Martin wrote: >> >>> If there's a recommended way to use the sti nodejs image for simply >>> running a node app, that'd be great. >>> I'll spend some time trying to figure it out as I can't find Usage docs >>> other than doing an sti build. >>> >> > Hi David, > what I did when testing sti-nodejs, was that I have build sti-base[1] from > scratch for rhel7. You will end up with openshift/base-rhel7 > build sti-nodejs afterwards you will have openshift/nodejs-010-rhel7 in > you local images list. Now you are ready to build&run your nodejs > application image with sti, like explained in usage[3]. > > > > > [1] - https://github.com/openshift/sti-base > [2] - https://github.com/openshift/sti-nodejs > [3] - > https://github.com/openshift/sti-nodejs/blob/master/0.10/.sti/bin/usage > > -- > Tomas Hrcka > Software Engineer - Developer Experience > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From davmarti at redhat.com Fri Aug 7 12:47:35 2015 From: davmarti at redhat.com (David Martin) Date: Fri, 7 Aug 2015 13:47:35 +0100 Subject: [scl.org] rhscl dockerfiles In-Reply-To: <55C48E6C.5010900@redhat.com> References: <55C348C9.8070808@redhat.com> <55C35EBF.9050401@redhat.com> <55C3785D.1070607@redhat.com> <55C4524F.5040803@redhat.com> <55C48E6C.5010900@redhat.com> Message-ID: Thanks Tomas, I got something working with this ``` FROM registry.access.redhat.com/openshift3/nodejs-010-rhel7 # Extract app to work dir .... # Other setup stuff ... CMD source /opt/openshift/etc/scl_enable; npm start ``` On Fri, Aug 7, 2015 at 11:54 AM, Tomas Hrcka wrote: > > > On 08/07/2015 11:07 AM, David Martin wrote: > > Thanks Tomas. > > Maybe my problem wasn't explained clearly enough. Apologies. > > I like to use a base nodejs image that behaves more like the one available > on docker hub https://hub.docker.com/_/node/ > as opposed to one that requires the sti tools. > > > You can use the sti tools just to build the nodejs010 base image. > Or pull it from internal registry > registry.access.redhat.com/openshift3/nodejs-010-rhel7 > > > e.g. I can use a Dockerfile like this to build a container for my app > > ``` > FROM nodejs > ADD . /usr/src/app > ``` > > and build your app using appropriate tag in FROM > > > > then do a `docker build` and I have my image for my app. > > > On Fri, Aug 7, 2015 at 7:38 AM, Tomas Hrcka wrote: > >> On 08/06/2015 05:08 PM, Honza Horak wrote: >> >>> Adding Tomas into CC, he maintains nodejs and has better knowledge what >>> it means to run nodejs app. >>> >>> My nodejs-unexperienced thought would be you can create a new docker >>> image, that will use `FROM: nodejs-010-rhel7` and: >>> * add the app code somewhere into the image (e.g. into /opt/app-root/app) >>> * changing CMD to run your application on pure `docker run` >>> >>> Or, theoretically, you don't have to create a new layer (image), just >>> use volume mounting to get your app into the container. It would mean to >>> run the image this way: >>> >>> #> docker run -v /your/app:/opt/app-root/app nodej-010-rhel7 >>> /opt/app-root/app/run.sh >>> >>> But I may be also wrong about how it is the best to do it. Or whether >>> this way is something we should or shouldn't recommend. >>> >>> Sharing also to the ML, maybe others might have different opinions/ideas >>> or at least issues. >>> >>> Honza >>> >>> On 08/06/2015 03:42 PM, David Martin wrote: >>> >>>> If there's a recommended way to use the sti nodejs image for simply >>>> running a node app, that'd be great. >>>> I'll spend some time trying to figure it out as I can't find Usage docs >>>> other than doing an sti build. >>>> >>> >> Hi David, >> what I did when testing sti-nodejs, was that I have build sti-base[1] >> from scratch for rhel7. You will end up with openshift/base-rhel7 >> build sti-nodejs afterwards you will have openshift/nodejs-010-rhel7 in >> you local images list. Now you are ready to build&run your nodejs >> application image with sti, like explained in usage[3]. >> >> >> >> >> [1] - https://github.com/openshift/sti-base >> [2] - https://github.com/openshift/sti-nodejs >> [3] - >> https://github.com/openshift/sti-nodejs/blob/master/0.10/.sti/bin/usage >> >> -- >> Tomas Hrcka >> Software Engineer - Developer Experience >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hhorak at redhat.com Wed Aug 12 08:56:41 2015 From: hhorak at redhat.com (Honza Horak) Date: Wed, 12 Aug 2015 10:56:41 +0200 Subject: [scl.org] [CentOS-devel] Log from CentOS SCLo SIG sync-up meeting on #centos-devel (2015-08-05) In-Reply-To: <55C238F2.90409@redhat.com> References: <55C22053.2040905@redhat.com> <55C238F2.90409@redhat.com> Message-ID: <55CB0A49.1040102@redhat.com> Not that soon as I wished, but here it is. Request for creating missing tags: https://bugs.centos.org/view.php?id=9228 Request for importing scl.org packages: https://bugs.centos.org/view.php?id=9229 Thomas, are there all information you need? I've also reported not-yet-working repository creation: https://bugs.centos.org/view.php?id=9219 Brian, any news with that one? ^ Honza On 08/05/2015 06:25 PM, Honza Horak wrote: > (06:22:05 PM) hhorak: so, I'll prepare the list of scl.org repos for > rhel6 and we can create one testing rhel6 scl first.. sounds fine? From noah at coderanger.net Sat Aug 15 21:49:57 2015 From: noah at coderanger.net (Noah Kantrowitz) Date: Sat, 15 Aug 2015 14:49:57 -0700 Subject: [scl.org] softwarecollections.org offline Message-ID: Anyone know whats up with it? --Noah -------------- 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 msuchy at redhat.com Mon Aug 17 08:17:05 2015 From: msuchy at redhat.com (=?UTF-8?Q?Miroslav_Such=c3=bd?=) Date: Mon, 17 Aug 2015 10:17:05 +0200 Subject: [scl.org] softwarecollections.org offline In-Reply-To: References: Message-ID: <55D19881.2080904@redhat.com> Dne 15.8.2015 v 23:49 Noah Kantrowitz napsal(a): > Anyone know whats up with it? I am working on this. -- Miroslav Suchy, RHCA Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys From rikske at deds.nl Mon Aug 17 14:38:38 2015 From: rikske at deds.nl (rikske at deds.nl) Date: Mon, 17 Aug 2015 16:38:38 +0200 Subject: [scl.org] softwarecollections.org offline In-Reply-To: <55D19881.2080904@redhat.com> References: <55D19881.2080904@redhat.com> Message-ID: <107c5f8da771fad3eecae4927f3095da.squirrel@deds.nl> I don't understand the purpose of softwarecollections.org? Where are the up-to-date sources of the SCL packages on git.centos.org? As you guys did before. Where are the RPMS on the centos.org mirrors in then folder SCL as before? As you guys did before. Softwarecollections.org only creates fragmentation. One site, one portal, one source and that should be *.centos.org! > Dne 15.8.2015 v 23:49 Noah Kantrowitz napsal(a): >> Anyone know whats up with it? > > I am working on this. > > -- > Miroslav Suchy, RHCA > Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > From msuchy at redhat.com Mon Aug 17 14:49:21 2015 From: msuchy at redhat.com (=?UTF-8?Q?Miroslav_Such=c3=bd?=) Date: Mon, 17 Aug 2015 16:49:21 +0200 Subject: [scl.org] softwarecollections.org offline In-Reply-To: <107c5f8da771fad3eecae4927f3095da.squirrel@deds.nl> References: <55D19881.2080904@redhat.com> <107c5f8da771fad3eecae4927f3095da.squirrel@deds.nl> Message-ID: <55D1F471.4020802@redhat.com> Dne 17.8.2015 v 16:38 rikske at deds.nl napsal(a): > I don't understand the purpose of softwarecollections.org? > > Where are the up-to-date sources of the SCL packages on git.centos.org? > As you guys did before. > > Where are the RPMS on the centos.org mirrors in then folder SCL as before? > As you guys did before. > > Softwarecollections.org only creates fragmentation. > One site, one portal, one source and that should be *.centos.org! There is not only Centos. You can have SCLs for other systems. E.g. old perl for latest Fedora. How you can get your bits to git.centos.org? The process is quite long and there is several approvals on the way. Compare it to Copr & softwarecollections.org: you can build and import your collections within few minutes. No approvals, no blockers. Just few clicks. -- Miroslav Suchy, RHCA Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys From langdon at redhat.com Mon Aug 17 14:55:47 2015 From: langdon at redhat.com (Langdon White) Date: Mon, 17 Aug 2015 10:55:47 -0400 Subject: [scl.org] softwarecollections.org offline In-Reply-To: <55D1F471.4020802@redhat.com> References: <55D19881.2080904@redhat.com> <107c5f8da771fad3eecae4927f3095da.squirrel@deds.nl> <55D1F471.4020802@redhat.com> Message-ID: <55D1F5F3.5060406@redhat.com> On 08/17/2015 10:49 AM, Miroslav Such? wrote: > Dne 17.8.2015 v 16:38 rikske at deds.nl napsal(a): >> I don't understand the purpose of softwarecollections.org? >> >> Where are the up-to-date sources of the SCL packages on git.centos.org? >> As you guys did before. >> >> Where are the RPMS on the centos.org mirrors in then folder SCL as before? >> As you guys did before. >> >> Softwarecollections.org only creates fragmentation. >> One site, one portal, one source and that should be *.centos.org! > There is not only Centos. You can have SCLs for other systems. E.g. old perl for latest Fedora. > > How you can get your bits to git.centos.org? The process is quite long and there is several approvals on the way. > Compare it to Copr & softwarecollections.org: you can build and import your collections within few minutes. > No approvals, no blockers. Just few clicks. > All that said, I would like to see content updates on scl.org once the centos-scl-sig is completely baked to indicate the relationship(s). langdon From hhorak at redhat.com Mon Aug 17 14:57:34 2015 From: hhorak at redhat.com (Honza Horak) Date: Mon, 17 Aug 2015 16:57:34 +0200 Subject: [scl.org] softwarecollections.org offline In-Reply-To: <55D1F471.4020802@redhat.com> References: <55D19881.2080904@redhat.com> <107c5f8da771fad3eecae4927f3095da.squirrel@deds.nl> <55D1F471.4020802@redhat.com> Message-ID: <55D1F65E.4020202@redhat.com> On 08/17/2015 04:49 PM, Miroslav Such? wrote: > Dne 17.8.2015 v 16:38 rikske at deds.nl napsal(a): >> I don't understand the purpose of softwarecollections.org? >> >> Where are the up-to-date sources of the SCL packages on git.centos.org? >> As you guys did before. >> >> Where are the RPMS on the centos.org mirrors in then folder SCL as before? >> As you guys did before. >> >> Softwarecollections.org only creates fragmentation. >> One site, one portal, one source and that should be *.centos.org! > > There is not only Centos. You can have SCLs for other systems. E.g. old perl for latest Fedora. > > How you can get your bits to git.centos.org? The process is quite long and there is several approvals on the way. > Compare it to Copr & softwarecollections.org: you can build and import your collections within few minutes. > No approvals, no blockers. Just few clicks. Well, that is true and copr will stay to be the easy build service for SCLs (and for Fedora SCLs until it is possible directly in http://koji.fedoraproject.org). But some of the collections from softwarecollections.org are still planned to move to centos.org. The process doesn't go as fast as I'd wish, but we're about to start mass rebuilding all the packages in cbs.centos.org. After this is done, softwarecollections.org will stay as one common site for collections packages. Honza From rikske at deds.nl Mon Aug 17 15:15:36 2015 From: rikske at deds.nl (rikske at deds.nl) Date: Mon, 17 Aug 2015 17:15:36 +0200 Subject: [scl.org] softwarecollections.org offline In-Reply-To: <55D1F65E.4020202@redhat.com> References: <55D19881.2080904@redhat.com> <107c5f8da771fad3eecae4927f3095da.squirrel@deds.nl> <55D1F471.4020802@redhat.com> <55D1F65E.4020202@redhat.com> Message-ID: <44f9b01624fe4edb06340180d84fb243.squirrel@deds.nl> Thanks for the info guys. P.s. Hopefully softwarecollections.org will work again quickly. An ETA for that? I need some packages :) > On 08/17/2015 04:49 PM, Miroslav Such? wrote: >> Dne 17.8.2015 v 16:38 rikske at deds.nl napsal(a): >>> I don't understand the purpose of softwarecollections.org? >>> >>> Where are the up-to-date sources of the SCL packages on git.centos.org? >>> As you guys did before. >>> >>> Where are the RPMS on the centos.org mirrors in then folder SCL as >>> before? >>> As you guys did before. >>> >>> Softwarecollections.org only creates fragmentation. >>> One site, one portal, one source and that should be *.centos.org! >> >> There is not only Centos. You can have SCLs for other systems. E.g. old >> perl for latest Fedora. >> >> How you can get your bits to git.centos.org? The process is quite long >> and there is several approvals on the way. >> Compare it to Copr & softwarecollections.org: you can build and import >> your collections within few minutes. >> No approvals, no blockers. Just few clicks. > > Well, that is true and copr will stay to be the easy build service for > SCLs (and for Fedora SCLs until it is possible directly in > http://koji.fedoraproject.org). > > But some of the collections from softwarecollections.org are still > planned to move to centos.org. The process doesn't go as fast as I'd > wish, but we're about to start mass rebuilding all the packages in > cbs.centos.org. After this is done, softwarecollections.org will stay as > one common site for collections packages. > > Honza > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > From noah at coderanger.net Mon Aug 17 18:50:05 2015 From: noah at coderanger.net (Noah Kantrowitz) Date: Mon, 17 Aug 2015 11:50:05 -0700 Subject: [scl.org] softwarecollections.org offline In-Reply-To: <44f9b01624fe4edb06340180d84fb243.squirrel@deds.nl> References: <55D19881.2080904@redhat.com> <107c5f8da771fad3eecae4927f3095da.squirrel@deds.nl> <55D1F471.4020802@redhat.com> <55D1F65E.4020202@redhat.com> <44f9b01624fe4edb06340180d84fb243.squirrel@deds.nl> Message-ID: <6454524C-80FB-42B5-A6D1-73BF08F84480@coderanger.net> Maybe progress? The server has changed from timing out to at least no longer listening on 80/443. Anyone have an ETA at this point? Been down two days at this point, any kind of status update would be nice. --Noah On Aug 17, 2015, at 8:15 AM, rikske at deds.nl wrote: > Thanks for the info guys. > > P.s. Hopefully softwarecollections.org will work again quickly. > An ETA for that? > I need some packages :) > >> On 08/17/2015 04:49 PM, Miroslav Such? wrote: >>> Dne 17.8.2015 v 16:38 rikske at deds.nl napsal(a): >>>> I don't understand the purpose of softwarecollections.org? >>>> >>>> Where are the up-to-date sources of the SCL packages on git.centos.org? >>>> As you guys did before. >>>> >>>> Where are the RPMS on the centos.org mirrors in then folder SCL as >>>> before? >>>> As you guys did before. >>>> >>>> Softwarecollections.org only creates fragmentation. >>>> One site, one portal, one source and that should be *.centos.org! >>> >>> There is not only Centos. You can have SCLs for other systems. E.g. old >>> perl for latest Fedora. >>> >>> How you can get your bits to git.centos.org? The process is quite long >>> and there is several approvals on the way. >>> Compare it to Copr & softwarecollections.org: you can build and import >>> your collections within few minutes. >>> No approvals, no blockers. Just few clicks. >> >> Well, that is true and copr will stay to be the easy build service for >> SCLs (and for Fedora SCLs until it is possible directly in >> http://koji.fedoraproject.org). >> >> But some of the collections from softwarecollections.org are still >> planned to move to centos.org. The process doesn't go as fast as I'd >> wish, but we're about to start mass rebuilding all the packages in >> cbs.centos.org. After this is done, softwarecollections.org will stay as >> one common site for collections packages. >> >> Honza >> >> _______________________________________________ >> 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: signature.asc Type: application/pgp-signature Size: 163 bytes Desc: Message signed with OpenPGP using GPGMail URL: From doran at bluehost.com Mon Aug 17 19:49:59 2015 From: doran at bluehost.com (Doran Barton) Date: Mon, 17 Aug 2015 13:49:59 -0600 Subject: [scl.org] softwarecollections.org offline In-Reply-To: References: Message-ID: <20150817134959.2a5ebd8c@doran-t440s> On Sat, 15 Aug 2015 14:49:57 -0700 Noah Kantrowitz wrote: > Anyone know whats up with it? I've spoken to Jared Smith here at Bluehost. He's the one who set up the box and the hosting account. He told me the server has been rebooted but he doesn't have SSH access to troubleshoot Apache. If someone wants to reach Jared, his e-mail address is jared.smith at endurance.com. -- Doran L. Barton - Senior Developer at Bluehost "Do you like bowling? Let's play bowling. Breaking down the pins and get hot communication." -- A sign in Japan From noah at coderanger.net Mon Aug 17 23:40:53 2015 From: noah at coderanger.net (Noah Kantrowitz) Date: Mon, 17 Aug 2015 16:40:53 -0700 Subject: [scl.org] softwarecollections.org offline In-Reply-To: <20150817134959.2a5ebd8c@doran-t440s> References: <20150817134959.2a5ebd8c@doran-t440s> Message-ID: <6D347185-FCC2-4094-821C-C03CEC8ECEBB@coderanger.net> On Aug 17, 2015, at 12:49 PM, Doran Barton wrote: > On Sat, 15 Aug 2015 14:49:57 -0700 > Noah Kantrowitz wrote: > >> Anyone know whats up with it? > > I've spoken to Jared Smith here at Bluehost. He's the one who set up the > box and the hosting account. He told me the server has been rebooted but he > doesn't have SSH access to troubleshoot Apache. If someone wants to reach > Jared, his e-mail address is jared.smith at endurance.com. Since Red Hat seems to be unable to provide any information on whats going on, does anyone have an internal mirror of the package data? We could get a skeleton copy of the packages themselves up on S3 or similar at least. --Noah -------------- 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 seitz at bsd-unix.net Tue Aug 18 01:05:30 2015 From: seitz at bsd-unix.net (Bryan Seitz) Date: Mon, 17 Aug 2015 21:05:30 -0400 Subject: [scl.org] softwarecollections.org offline In-Reply-To: <6D347185-FCC2-4094-821C-C03CEC8ECEBB@coderanger.net> References: <20150817134959.2a5ebd8c@doran-t440s> <6D347185-FCC2-4094-821C-C03CEC8ECEBB@coderanger.net> Message-ID: <20150818010530.GA63644@bsd-unix.net> On Mon, Aug 17, 2015 at 04:40:53PM -0700, Noah Kantrowitz wrote: > > On Aug 17, 2015, at 12:49 PM, Doran Barton wrote: > > > On Sat, 15 Aug 2015 14:49:57 -0700 > > Noah Kantrowitz wrote: > > > >> Anyone know whats up with it? > > > > I've spoken to Jared Smith here at Bluehost. He's the one who set up the > > box and the hosting account. He told me the server has been rebooted but he > > doesn't have SSH access to troubleshoot Apache. If someone wants to reach > > Jared, his e-mail address is jared.smith at endurance.com. > > Since Red Hat seems to be unable to provide any information on whats going on, does anyone have an internal mirror of the package data? We could get a skeleton copy of the packages themselves up on S3 or similar at least. I would but... they never provided rsync even though I asked a few times :) -- Bryan G. Seitz From smooge at gmail.com Tue Aug 18 01:05:50 2015 From: smooge at gmail.com (Stephen John Smoogen) Date: Mon, 17 Aug 2015 19:05:50 -0600 Subject: [scl.org] softwarecollections.org offline In-Reply-To: <6D347185-FCC2-4094-821C-C03CEC8ECEBB@coderanger.net> References: <20150817134959.2a5ebd8c@doran-t440s> <6D347185-FCC2-4094-821C-C03CEC8ECEBB@coderanger.net> Message-ID: On 17 August 2015 at 17:40, Noah Kantrowitz wrote: > > On Aug 17, 2015, at 12:49 PM, Doran Barton wrote: > >> On Sat, 15 Aug 2015 14:49:57 -0700 >> Noah Kantrowitz wrote: >> >>> Anyone know whats up with it? >> >> I've spoken to Jared Smith here at Bluehost. He's the one who set up the >> box and the hosting account. He told me the server has been rebooted but he >> doesn't have SSH access to troubleshoot Apache. If someone wants to reach >> Jared, his e-mail address is jared.smith at endurance.com. > > Since Red Hat seems to be unable to provide any information on whats going on, does anyone have an internal mirror of the package data? We could get a skeleton copy of the packages themselves up on S3 or similar at least. > I don't know of any mirrors of this. I will be bringing this up tomorrow to get this better hosted and dealt with. > --Noah > > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > -- Stephen J Smoogen. From msuchy at redhat.com Tue Aug 18 07:25:50 2015 From: msuchy at redhat.com (=?UTF-8?Q?Miroslav_Such=c3=bd?=) Date: Tue, 18 Aug 2015 09:25:50 +0200 Subject: [scl.org] softwarecollections.org offline In-Reply-To: References: Message-ID: <55D2DDFE.4000000@redhat.com> Dne 15.8.2015 v 23:49 Noah Kantrowitz napsal(a): > Anyone know whats up with it? It is online again. I will post post-mortem soon. -- Miroslav Suchy, RHCA Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys From msuchy at redhat.com Tue Aug 18 08:30:16 2015 From: msuchy at redhat.com (=?UTF-8?Q?Miroslav_Such=c3=bd?=) Date: Tue, 18 Aug 2015 10:30:16 +0200 Subject: [scl.org] softwarecollections.org offline - post mortem In-Reply-To: References: Message-ID: <55D2ED18.6090908@redhat.com> For all those who are curious what happened to softwarecollections.org - here is timeline and description of the problem: All times are in CEST timezone (which is UTC+2) 2015-08-15 14:22 - OOM killer is starting killing processes (mostly http and createrepo_c). Why? I do not know yet, probably some bug in our application, we will investigate it as soon as possible. 2015-08-15 18:28 - monitoring reports that web server is down. But since this is not marked as critical service and it happen during weekend it have to wait till Monday. 2015-08-17 ~9:00 - I am starting to investigate what happen. Ports are open, but all communication timeouts. I'm trying to get somebody who will try to restart that machine. This machine is hosted by BlueHost, which donated this machine and connectivity for free. I am talking to Support via WebChat and describing the problem. The person on the other side demands some kind of authentication (login and some letters from password). But I have no such credentials as this server was donated out of normal process and we got no such credentials. Just server with our ssh keys. I am redirected to support at bluehost.com. Concurrently I'm trying to notice JSmith, who is my only point of contact at BlueHost, but since he is in different TZ and he can be on vacation (very likely during summer) I'm placing my bet on BlueHost support. 2015-08-17 10:16 - I got automatic reply from support at bluehost.com that this email is discontinued and I should open my ticket on BlueHost website. Few moments later I found that I need account to log to ticket system (sounds like Catch-22). 2015-08-17 10:53 - I used my personal credit card and I'm paying for the cheapest service of Bluehost so I can get some credentials (still it is $86). 2015-08-17 10:57 - I filed ticket HJZ-99465-311 2015-08-17 15:21 - JSmith responded over IRC, I'm describing the situation, he noticed some admin 2015-08-17 17:05 - I'm heading home from office, no updates from BlueHost or JSmith so far 2015-08-17 20:10 - server was restarted, for unknown reason httpd service is not enable therefore it did not start automatically after reboot. 2015-08-17 9:27 - I enabled and started httpd service and softwarecollection.org is back online This incident revealed several problems on both Red Hat and BlueHost side and in upcoming days we will work on our processes so this will not happen again. I'm sorry for the problems it caused you. -- Miroslav Suchy, RHCA Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys From daniel.davis at nih.gov Tue Aug 18 14:33:59 2015 From: daniel.davis at nih.gov (Davis, Daniel (NIH/NLM) [C]) Date: Tue, 18 Aug 2015 14:33:59 +0000 Subject: [scl.org] issue tracking for rh-python34 Message-ID: Since I last checked months ago, there's now a Python 3.4.2 in Software Collections - https://www.softwarecollections.org/en/scls/rhscl/rh-python34/. The "Issue Tracker" URL on SoftwareCollections.org directs me to the community product "softwarecollections.org" at https://bugzilla.redhat.com, which doesn't include rh-python34 as a component. I login with my preexisting account. Using my rad skills, I find that in Advanced Search under classification "Red Hat" product "Red Hat Software Collections", there's a component "rh-python34". So, who can update the link to the issue tracker to point to the correct Product? Thanks, Dan Davis, Systems/Applications Architect (Contractor), Office of Computer and Communications Systems, National Library of Medicine, NIH -------------- next part -------------- An HTML attachment was scrubbed... URL: From hhorak at redhat.com Tue Aug 18 17:55:10 2015 From: hhorak at redhat.com (Honza Horak) Date: Tue, 18 Aug 2015 19:55:10 +0200 Subject: [scl.org] maven30 issues Message-ID: <55D3717E.5040109@redhat.com> Hi Thomas, I've got unexpected error in maven30 build: https://cbs.centos.org/koji/taskinfo?taskID=19431 release mismatch (build: 0.bootstrap1.24.el7, rpm: 0.bootstrap1.24.el7.centos if I'm supposed to build only packages with el7.centos as %dist, it's weird that I don't see it in other builds.. now I'm thinking whether maven30 might be configured differently or whether other tags are supposed to be configured that same way.. any idea? Honza From ncoghlan at redhat.com Wed Aug 19 00:54:10 2015 From: ncoghlan at redhat.com (Nick Coghlan) Date: Wed, 19 Aug 2015 10:54:10 +1000 Subject: [scl.org] Integrating SCLs with tools like DevAssistant? Message-ID: I started a new Django project with DevAssistant today, and it offered me the option of making it a Python 3 project rather than a Python 2 one. However, this was just choosing between the parallel stacks included as part of the main Fedora distribution. It occurs to me - might it make sense for the SCL project to figure out a way for tools like DevAssistant to access a list of all of the software collections installed for a particular language runtime, and thus allow a developer to easily choose which one they want to use as the basis for a new project? Using containers for deployment doesn't eliminate that basic need to choose the language runtime to include in the container along with the application, and at least for Python, there's currently still going to need to be a "system Python runtime" and an "application Python runtime" installed in parallel inside the container. Cheers, Nick. -------------- next part -------------- An HTML attachment was scrubbed... URL: From hhorak at redhat.com Wed Aug 19 14:51:56 2015 From: hhorak at redhat.com (Honza Horak) Date: Wed, 19 Aug 2015 16:51:56 +0200 Subject: [scl.org] CentOS SCLo SIG sync-up meeting on #centos-devel (2015-08-19) Message-ID: <55D4980C.4090305@redhat.com> SCLo SIG meeting will be at 15: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 = * cbs builds going, sharing status * dist-git repos creation -- any update? https://bugs.centos.org/view.php?id=9219 * docker images based on SCL packages built in cbs how/where to build them? who can push them into docker hub? Honza From mstuchli at redhat.com Thu Aug 20 12:58:41 2015 From: mstuchli at redhat.com (Matej Stuchlik) Date: Thu, 20 Aug 2015 08:58:41 -0400 (EDT) Subject: [scl.org] issue tracking for rh-python34 In-Reply-To: References: Message-ID: <1369869842.13120394.1440075521811.JavaMail.zimbra@redhat.com> Thank you for the report Dan, I've added rh-python34 to the list of components. :) Matt ----- Original Message ----- > From: "Daniel Davis (NIH/NLM) [C]" > To: sclorg at redhat.com > Sent: Tuesday, August 18, 2015 4:33:59 PM > Subject: [scl.org] issue tracking for rh-python34 > > > > Since I last checked months ago, there?s now a Python 3.4.2 in Software > Collections - https://www.softwarecollections.org/en/scls/rhscl/rh-python34/ > . > > > > The ?Issue Tracker? URL on SoftwareCollections.org directs me to the > community product ?softwarecollections.org? at https://bugzilla.redhat.com , > which doesn?t include rh-python34 as a component. > > I login with my preexisting account. Using my rad skills, I find that in > Advanced Search under classification ?Red Hat? product ?Red Hat Software > Collections?, there?s a component ?rh-python34?. > > > > So, who can update the link to the issue tracker to point to the correct > Product? > > > > Thanks, > > > > 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 noah at coderanger.net Fri Aug 28 23:54:03 2015 From: noah at coderanger.net (Noah Kantrowitz) Date: Fri, 28 Aug 2015 16:54:03 -0700 Subject: [scl.org] Node010 broken on EL6 Message-ID: <33A8D34D-F53B-4286-A361-70DB50F63638@coderanger.net> After installing the v8314 collection, nodejs010 fails to install: Error: Package: nodejs010-npm-1.4.28-3.el6.noarch (rhscl-nodejs010-epel-6-x86_64) Requires: nodejs010-npm(read-installed) >= 2.0.5 Installing: nodejs010-nodejs-read-installed-0.2.4-1.el6.noarch (rhscl-nodejs010-epel-6-x86_64) nodejs010-npm(read-installed) = 0.2.4 Works fine on EL7. No idea where to report this since I can't find specific owners, so here y'all go :) --Noah -------------- 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 msuchy at redhat.com Mon Aug 31 07:14:07 2015 From: msuchy at redhat.com (=?UTF-8?Q?Miroslav_Such=c3=bd?=) Date: Mon, 31 Aug 2015 09:14:07 +0200 Subject: [scl.org] Node010 broken on EL6 In-Reply-To: <33A8D34D-F53B-4286-A361-70DB50F63638@coderanger.net> References: <33A8D34D-F53B-4286-A361-70DB50F63638@coderanger.net> Message-ID: <55E3FEBF.70302@redhat.com> Dne 29.8.2015 v 01:54 Noah Kantrowitz napsal(a): > After installing the v8314 collection, nodejs010 fails to install: > > Error: Package: nodejs010-npm-1.4.28-3.el6.noarch (rhscl-nodejs010-epel-6-x86_64) > Requires: nodejs010-npm(read-installed) >= 2.0.5 > Installing: nodejs010-nodejs-read-installed-0.2.4-1.el6.noarch (rhscl-nodejs010-epel-6-x86_64) > nodejs010-npm(read-installed) = 0.2.4 > > Works fine on EL7. No idea where to report this since I can't find specific owners, so here y'all go :) https://www.softwarecollections.org/en/scls/rhscl/nodejs010/ There is a button "Issue Tracker". -- Miroslav Suchy, RHCA Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys From daniel.davis at nih.gov Mon Aug 31 14:27:26 2015 From: daniel.davis at nih.gov (Davis, Daniel (NIH/NLM) [C]) Date: Mon, 31 Aug 2015 14:27:26 +0000 Subject: [scl.org] Node010 broken on EL6 In-Reply-To: <55E3FEBF.70302@redhat.com> References: <33A8D34D-F53B-4286-A361-70DB50F63638@coderanger.net> <55E3FEBF.70302@redhat.com> Message-ID: To expand on what Miroslav says, Each "approved" software collection is supposed to have an "Issue Tracker", and most point to https://bugzilla.redhat.com/ and the product "softwarecollections.org". On https://bugzilla.redhat.com, under the product "softwarecollections.org", there is a component "nodejs010" and another "v8314". Miroslav, I see that you are a builder and admin of nodejs010 after logging in to COPR via my fledgling Fedora Project membership - that suggests that you are one of the owners - yes? Dan Davis, Systems/Applications Architect (Contractor), Office of Computer and Communications Systems, National Library of Medicine, NIH -----Original Message----- From: sclorg-bounces at redhat.com [mailto:sclorg-bounces at redhat.com] On Behalf Of Miroslav Such? Sent: Monday, August 31, 2015 3:14 AM To: sclorg at redhat.com Subject: Re: [scl.org] Node010 broken on EL6 Dne 29.8.2015 v 01:54 Noah Kantrowitz napsal(a): > After installing the v8314 collection, nodejs010 fails to install: > > Error: Package: nodejs010-npm-1.4.28-3.el6.noarch (rhscl-nodejs010-epel-6-x86_64) > Requires: nodejs010-npm(read-installed) >= 2.0.5 > Installing: nodejs010-nodejs-read-installed-0.2.4-1.el6.noarch (rhscl-nodejs010-epel-6-x86_64) > nodejs010-npm(read-installed) = 0.2.4 > > Works fine on EL7. No idea where to report this since I can't find specific owners, so here y'all go :) https://www.softwarecollections.org/en/scls/rhscl/nodejs010/ There is a button "Issue Tracker". -- Miroslav Suchy, RHCA Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys _______________________________________________ SCLorg mailing list SCLorg at redhat.com https://www.redhat.com/mailman/listinfo/sclorg From asamalik at redhat.com Mon Aug 31 14:56:02 2015 From: asamalik at redhat.com (Adam Samalik) Date: Mon, 31 Aug 2015 16:56:02 +0200 Subject: [scl.org] Node010 broken on EL6 In-Reply-To: References: <33A8D34D-F53B-4286-A361-70DB50F63638@coderanger.net> <55E3FEBF.70302@redhat.com> Message-ID: Hi, I build and maintain these collections. I have checked nodejs010 and noted that the nodejs010-nodejs-read-installed is not built correctly for el6. I'm submitting a rebuild to fix this issue. Adam On Mon, Aug 31, 2015 at 4:27 PM, Davis, Daniel (NIH/NLM) [C] < daniel.davis at nih.gov> wrote: > To expand on what Miroslav says, > > Each "approved" software collection is supposed to have an "Issue > Tracker", and most point to https://bugzilla.redhat.com/ and the product " > softwarecollections.org". On https://bugzilla.redhat.com, under the > product "softwarecollections.org", there is a component "nodejs010" and > another "v8314". > > Miroslav, I see that you are a builder and admin of nodejs010 after > logging in to COPR via my fledgling Fedora Project membership - that > suggests that you are one of the owners - yes? > > Dan Davis, Systems/Applications Architect (Contractor), > Office of Computer and Communications Systems, > National Library of Medicine, NIH > > -----Original Message----- > From: sclorg-bounces at redhat.com [mailto:sclorg-bounces at redhat.com] On > Behalf Of Miroslav Such? > Sent: Monday, August 31, 2015 3:14 AM > To: sclorg at redhat.com > Subject: Re: [scl.org] Node010 broken on EL6 > > Dne 29.8.2015 v 01:54 Noah Kantrowitz napsal(a): > > After installing the v8314 collection, nodejs010 fails to install: > > > > Error: Package: nodejs010-npm-1.4.28-3.el6.noarch > (rhscl-nodejs010-epel-6-x86_64) > > Requires: nodejs010-npm(read-installed) >= 2.0.5 > > Installing: > nodejs010-nodejs-read-installed-0.2.4-1.el6.noarch > (rhscl-nodejs010-epel-6-x86_64) > > nodejs010-npm(read-installed) = 0.2.4 > > > > Works fine on EL7. No idea where to report this since I can't find > specific owners, so here y'all go :) > > https://www.softwarecollections.org/en/scls/rhscl/nodejs010/ > There is a button "Issue Tracker". > > -- > Miroslav Suchy, RHCA > Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys > > _______________________________________________ > 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 > -- Adam ?amal?k --------------------------- Associate Software Engineer Red Hat -------------- next part -------------- An HTML attachment was scrubbed... URL: From asamalik at redhat.com Mon Aug 31 15:05:50 2015 From: asamalik at redhat.com (Adam Samalik) Date: Mon, 31 Aug 2015 17:05:50 +0200 Subject: [scl.org] Node010 broken on EL6 In-Reply-To: References: <33A8D34D-F53B-4286-A361-70DB50F63638@coderanger.net> <55E3FEBF.70302@redhat.com> Message-ID: Should be OK now. Adam On Mon, Aug 31, 2015 at 4:56 PM, Adam Samalik wrote: > Hi, > > I build and maintain these collections. I have checked nodejs010 and noted > that the nodejs010-nodejs-read-installed is not built correctly for el6. > I'm submitting a rebuild to fix this issue. > > Adam > > On Mon, Aug 31, 2015 at 4:27 PM, Davis, Daniel (NIH/NLM) [C] < > daniel.davis at nih.gov> wrote: > >> To expand on what Miroslav says, >> >> Each "approved" software collection is supposed to have an "Issue >> Tracker", and most point to https://bugzilla.redhat.com/ and the product >> "softwarecollections.org". On https://bugzilla.redhat.com, under the >> product "softwarecollections.org", there is a component "nodejs010" and >> another "v8314". >> >> Miroslav, I see that you are a builder and admin of nodejs010 after >> logging in to COPR via my fledgling Fedora Project membership - that >> suggests that you are one of the owners - yes? >> >> Dan Davis, Systems/Applications Architect (Contractor), >> Office of Computer and Communications Systems, >> National Library of Medicine, NIH >> >> -----Original Message----- >> From: sclorg-bounces at redhat.com [mailto:sclorg-bounces at redhat.com] On >> Behalf Of Miroslav Such? >> Sent: Monday, August 31, 2015 3:14 AM >> To: sclorg at redhat.com >> Subject: Re: [scl.org] Node010 broken on EL6 >> >> Dne 29.8.2015 v 01:54 Noah Kantrowitz napsal(a): >> > After installing the v8314 collection, nodejs010 fails to install: >> > >> > Error: Package: nodejs010-npm-1.4.28-3.el6.noarch >> (rhscl-nodejs010-epel-6-x86_64) >> > Requires: nodejs010-npm(read-installed) >= 2.0.5 >> > Installing: >> nodejs010-nodejs-read-installed-0.2.4-1.el6.noarch >> (rhscl-nodejs010-epel-6-x86_64) >> > nodejs010-npm(read-installed) = 0.2.4 >> > >> > Works fine on EL7. No idea where to report this since I can't find >> specific owners, so here y'all go :) >> >> https://www.softwarecollections.org/en/scls/rhscl/nodejs010/ >> There is a button "Issue Tracker". >> >> -- >> Miroslav Suchy, RHCA >> Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys >> >> _______________________________________________ >> 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 >> > > > > -- > > Adam ?amal?k > --------------------------- > Associate Software Engineer > Red Hat > -- Adam ?amal?k --------------------------- Associate Software Engineer Red Hat -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel.davis at nih.gov Mon Aug 31 16:05:46 2015 From: daniel.davis at nih.gov (Davis, Daniel (NIH/NLM) [C]) Date: Mon, 31 Aug 2015 16:05:46 +0000 Subject: [scl.org] Errata publication and format Message-ID: My system administrators use https://github.com/liedekef/spacewalk_scripts/blob/master/centos-clone-errata.sh to clone CentOS errata. I've seen https://rhn.redhat.com/errata/rhel-6-rhscl-1-errata.html and found Software Collections in the general list of advisories. Where are errata published for Software collections as they come up? This list? I will happily clone that repository and teach it how to import software collections errata, allowing the user to specify which collections are of interest... Dan Davis, Systems/Applications Architect (Contractor), Office of Computer and Communications Systems, National Library of Medicine, NIH -------------- next part -------------- An HTML attachment was scrubbed... URL: From ian_veach at nshe.nevada.edu Mon Aug 31 21:27:18 2015 From: ian_veach at nshe.nevada.edu (Ian Veach) Date: Mon, 31 Aug 2015 14:27:18 -0700 Subject: [scl.org] SCL... for ppc? Message-ID: We run RHEL on IBM pSeries (ppc64) - which is mostly all types of awesome. However. Is there any future for SCL on a ppc platform? I'm specifically looking at PHP, which is 5.4.16 for RHEL7. Unfortunately, PHP 5.4 is being EOL'd in a couple weeks, and while RH will support 5.4 with security patches...only.... RHEL 8 is not even in sight, and applications will be requiring higher versions of PHP. I'd love to offer our customers a "modern" PHP in the next year... but other than us going back to compiling our own stack... Thanks for any info or even rumours or innuendo. :) cheers and thanks, Ian Veach, Senior Systems Analyst System Computing Services, Nevada System of Higher Education -- PUBLIC RECORDS NOTICE: In accordance with NRS Chapter 239, this email and responses, unless otherwise made confidential by law, may be subject to the Nevada Public Records laws and may be disclosed to the public upon request. -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel.davis at nih.gov Mon Aug 31 21:42:15 2015 From: daniel.davis at nih.gov (Davis, Daniel (NIH/NLM) [C]) Date: Mon, 31 Aug 2015 21:42:15 +0000 Subject: [scl.org] SCL... for ppc? In-Reply-To: References: Message-ID: I cannot answer that question, but I can suggest a strategy I?ve used over the years in absence of that. That is to download an SRPM from upstream, unpack it, patch the spec. file, and build it. At one time, I had automated cron jobs that looked for new packages and sent me email about stuff I needed to build for my platform ? the manual building was not so hard, but checking what needed to be built was rather a chore. I?m a baby Fedora Project member myself, and I just created my first Fedora Copr project hoping to answer the question whether PPM is an available architecture. I didn?t see a box for architecture, but maybe I?m just missing it ? if it is there, you might well be able to just rebuild on Fedora Copr and the repositories would be available to you. Dan Davis, Systems/Applications Architect (Contractor), Office of Computer and Communications Systems, National Library of Medicine, NIH From: sclorg-bounces at redhat.com [mailto:sclorg-bounces at redhat.com] On Behalf Of Ian Veach Sent: Monday, August 31, 2015 5:27 PM To: sclorg at redhat.com Subject: [scl.org] SCL... for ppc? We run RHEL on IBM pSeries (ppc64) - which is mostly all types of awesome. However. Is there any future for SCL on a ppc platform? I'm specifically looking at PHP, which is 5.4.16 for RHEL7. Unfortunately, PHP 5.4 is being EOL'd in a couple weeks, and while RH will support 5.4 with security patches...only.... RHEL 8 is not even in sight, and applications will be requiring higher versions of PHP. I'd love to offer our customers a "modern" PHP in the next year... but other than us going back to compiling our own stack... Thanks for any info or even rumours or innuendo. :) cheers and thanks, Ian Veach, Senior Systems Analyst System Computing Services, Nevada System of Higher Education PUBLIC RECORDS NOTICE: In accordance with NRS Chapter 239, this email and responses, unless otherwise made confidential by law, may be subject to the Nevada Public Records laws and may be disclosed to the public upon request. -------------- next part -------------- An HTML attachment was scrubbed... URL: