March 2016 - devel - lists.centos.org

ksplice and CentOS
by Karanbir Singh 25 Sep '25

25 Sep '25

hi guys, lots of people on this list are keen on contributing to the CentOS effort - and one place where we could, as a group of people, make a massive difference is being able to deliver a ksplice upgrade model. A couple of people have started in silo's to try and get something together but I feel it might be a good time to try and see if we can do somethng as a group. Do we have people on the list who find the idea of rebootless kernel upgrades interesting ? Is there some desire to try and make that happen within the CentOS Ecosystem ? - KB

24 47

anaconda dependency calculation?
by Nicholas Byrne 04 Aug '25

04 Aug '25

Hi all, I'm trying to find a tool that calculates all dependencies for a specific package or group of packages for use with CentOS 5 (beta) with the intention of putting together a custom single CD build of CentOS 5. With CentOS 4 i used a python script that used the hdrlist module to find all dependencies which borrowed code from a number of sources. I've looked at yumdownloader and how it checks dependencies (using the --resolve option) but if i pass it the list of packages defined in say the Base and the Core yum groups which generally form an absolute minimal install i end up with about 200 packages. If i do a custom install (using beta 1 disks) and deselect everything i end up with over 300 packages. So i'm guessing anaconda calculates dependencies in a slightly different way, can anyone point me to files/code where i should be looking to find out? Thanks very much in advance for help Nick This e-mail is the property of Quadriga Worldwide Ltd, intended for the addressee only and confidential. Any dissemination, copying or distribution of this message or any attachments is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from Quadriga may be monitored. Quadriga cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of Quadriga.

6 11

forums + portal for {lang}.centos.org sites
by Karanbir Singh 16 Aug '24

16 Aug '24

Hi, Earlier in the evening today Ralph, Fabian and I had a chat about the present state of the language subsites. This email sort of summarises the main issue ( s/w ). We seem to have run into a slight technical hitch with punbb/fluxbb. They dont support LDAP as a backend. And we had decided a few months back that all new rollouts must have ldap backend so we can rollin CentOS-DS / openldap based backend. So we need to look at alternatives, and since the primary focus of these international sites is going be forums : Here is a shortlist ( if there is anything else that people are aware of, please add to this list ) - phpBB - SMF - Fudforum - phorum - fluxbb Requirements: - Must be able to scale ( couple of hundred thousand msgs ) - Must be able to handle ldap auth ( if it cant, whats involved in writing the ldap-auth portion ) - Must address the specific requirements raised by the present www.centos.org forum users ( Can you please fill this section in ? ) - Must support all languages we need ( pure utf8 support would be good ) - Secure - Skin'able Nice to have: - Capable of running multiple instances from a single deployment - responsive community :D Things we will need to do: - Decide on what s/w to use. - Give the ArtWork people enough time to get the look & feel sorted. - Migrate newbb forums from www.centos.org to $system ( hey, english is a language too :D ). - Migrate fr.centos.org into the final s/w - setup {de/es/ja/it/pt_br}.centos.org Actions: Ralph and Fabian are going to work on setting up a test ldap server, once that is online we will then start by installing into our test-vm-farm the various s/w to eval them. If anyone would like to help, please feel free to jump right in. I'll setup a wiki page for this issue, which might be a good place to track progress. -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

22 81

CentOS 7.2 cloud images for ppc64le
by Xiandong Meng 14 Jun '16

14 Jun '16

Hi all, I noticed that there are centos 7 cloud images for x86. But i did not find the cloud images for ppc64le. Are there any work on it within this community? Or is there any plan to work on it? Regards, Xiandong Meng <mengxiandong(a)gmail.com> mengxiandong(a)gmail.com

2 6

Curating containers
by Karanbir Singh 04 Apr '16

04 Apr '16

hi, Yesterday a few of us met for a face to face walk through of the CentOS Container Pipeline we've been talking about. The aim was to rescope the upstream projects we can lean on, share code with, and help - and then find the glue pieces that could bring this code base together. The larger picture effectively boils down to : - Find the components needed to track code git repos ( either in git.centos.org or elsewhere ) - Find the components needed to now build that code, containerise the code, push it through a test process, and then deliver the containers either locally into a centos transitional container registry, or to a CDN like wider centos registry or if the user so desires, to a third part registry ( provided a good process can be find to handle the credentials needed ). - We'd want to use this pipeline both internally, for the CentOS Linux components ( eg. a LAMP container from CentOS Linux 7 ), for SIG components via cbs output ( eg. SCLo SIG folks shipping containers for their content ), as well as open this up via a trivial UI, for anyone in the community who'd like to come and consume this pipeline. the key piece that we didnt have clarity on was the orchestration and glue that could bind the various software components. Vaclav Pavlin, brought up that we might be able to use openshift templates in order to get the job runs done - if the input for the templates could be derived from the cccp-index, either via the jjb work already done, or writing a new filter into JJB, we might be able to execute a fairly scaleable solution without needing to own any piece of the over all code. Additionally, there is a fair interest from the Fedora team ( ie Adam! ) working on the same problem in their space, mostly consuming the identical code stack, within and for their infra, their constraints and aims. Over the coming days we are going to try and work though PoC's, get some infra setup and trial running through some of the user stories we want to execute on. Finally, a quick shout out to everyone for coming together at pretty much the last minute adhoc meeting - Fabian Arrotin, Brian Stinson, Christoph Goern, Vaclav Pavlin, Aaron Weitekamp, Tomas Tomecek, Adam Miller, Dusty Mabe, Honza Horak, Radek Vokal as well as Tim Waugh, Bama Charan and Mohammed Zeeshan for dialing into the meeting. And to everyone else, want to build containers with us ? come talk to us - we'd love to make sure we include as many user stories to get great scope before we start implementing bits. regards -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc

8 24

[RFE] subscription-manager in CentOS6
by Baptiste Agasse 04 Apr '16

04 Apr '16

Hi, I tried to speak about this to Johnny at the end of the last CentOS Dojo in Brussels, but he have to go. There is any chance that you to include subscription-manager in CentOS 6 ? We use foreman/katello, all work out of the box for centos 7 but it's not easy to manage additional installation repos in foreman/katello to manage that in one generic kickstart template for our deployments (multiple DCs, with multiple repos mirrors per locations...). As i see in the git repo of CentOS 7 [1], there is only few changes, like debranding. I see that redhat provides SRPMS for subscription-manager as well for RHEL6 [2] and versions of subscription-manager are are not so far from each other: RHEL 7 / CentOS 7 : subscription-manager 1.15.9 RHEL 6 : subscription-manager 1.14.10 I didn't take a look deeper at this time, but if there is any chance that you decide to include subscription-manager in CentOS 6 base repo and installation tree like in CentOS 7, i can take a look deeper to see if patches that are made for C7 are compatible with RHEL 6 subscription manager, and if not, backport them to c6. Have a nice day. Regards. [1] https://git.centos.org/tree/rpms!subscription-manager.git/refs!heads!c7 [2] ftp://ftp.redhat.com/redhat/linux/enterprise/6Server/en/os/SRPMS/ -- Baptiste

2 2

Problem installing golang.x86_64 with virt7-docker-common-candidate.
by centos-devel 01 Apr '16

01 Apr '16

First off- Thanks to all for reading and especially to Jan for responding so helpfully. So I realised that I could maybe make some progress by telling yum to ignore go version 1.5 from virt7-testing and just install the older 1.4 branch from extras. [root@vm139 admin]# yum --disablerepo base --disablerepo virt7-testing --skip-broken install golang Of course that just worked. :-) Having reread Jans first email again, > > godep go run make_secret.go -crt /tmp/nginx.crt -key /tmp/nginx.key > > > /tmp/secret.json > > godep: No Godeps found (or in any parent directory) > > make: *** [secret] Error 1 > > It says you are running godep in a directory where there is no Godeps > file. Once the binary is compiled, you don't need golang compiler. and read a bit more about godeps, I thought I would try without it to see if I could get past that error. So I just edited the Makefile: https://github.com/kubernetes/kubernetes/blob/release-1.2/examples/https-ng… to remove the call to godeps from: godep go run make_secret.go -crt $(CERT) -key $(KEY) > $(SECRET) to: go run make_secret.go -crt $(CERT) -key $(KEY) > $(SECRET) But that just spews errors that go can't find the dependencies it needs. well, DUH! I suppose those are meant to be listed in the Godeps file that godeps is complaining that it cannot find. As I said - this is new to me as I have not (yet) programmed in go. What do other people think? Does anyone more knowlegable than me about Kubernetes or Go have any suggestions? Perhaps I should submit a bug to github-kubernetes and move on? Thanks again to all for reading and especially to Jan for responding so helpfully. Colin. p.s. What I learned: Using CBS virt7-testing to provide docker and kubernetes Package: golang-1.5.1-1.el7.x86_64 will not install because it Requires: golang-src = 1.5.1-1.el7

2 1

centos git web front-end
by Phil Wyett 31 Mar '16

31 Mar '16

Hi all, What if any plans are in the pipeline for improving the web front-end of git.centos.org? Current issues: * Slow. * No search as page claims: none of your repositories are configured for Lucene indexing * Clicking on the 'repositories' link, hangs firefox because of how many entries are being listed by default. Could this be a static page with alphanumeric index that a user can click on depending on first character of package they wish to find? Regards Phil

4 6

Problem installing golang.x86_64 with virt7-docker-common-candidate
by centos-devel 30 Mar '16

30 Mar '16

Hi Jan. > I see now. The golang-src is provided by more repositories: > virt7-testing and base. Try: > yum install golang --disable-repo base [root@vm139 admin]# yum --disablerepo base install golang Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * extras: mirror.cov.ukservers.com * updates: repo.bigstepcloud.com Resolving Dependencies --> Running transaction check ---> Package golang.x86_64 0:1.5.1-1.el7 will be installed --> Processing Dependency: golang-src = 1.5.1-1.el7 for package: golang-1.5.1-1.el7.x86_64 --> Processing Dependency: golang-bin for package: golang-1.5.1-1.el7.x86_64 --> Processing Dependency: go-srpm-macros for package: golang-1.5.1-1.el7.x86_64 --> Running transaction check ---> Package go-srpm-macros.noarch 0:2-3.el7 will be installed ---> Package golang.x86_64 0:1.5.1-1.el7 will be installed --> Processing Dependency: golang-src = 1.5.1-1.el7 for package: golang-1.5.1-1.el7.x86_64 ---> Package golang-bin.x86_64 0:1.5.1-1.el7 will be installed --> Finished Dependency Resolution Error: Package: golang-1.5.1-1.el7.x86_64 (virt7-testing) Requires: golang-src = 1.5.1-1.el7 Available: golang-src-1.4.2-1.el7.centos.noarch (extras) golang-src = 1.4.2-1.el7.centos You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [root@vm139 admin]# [root@vm139 admin]# yum --disablerepo base --disablerepo extras install golang Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * updates: repo.bigstepcloud.com Resolving Dependencies --> Running transaction check ---> Package golang.x86_64 0:1.5.1-1.el7 will be installed --> Processing Dependency: golang-src = 1.5.1-1.el7 for package: golang-1.5.1-1.el7.x86_64 --> Processing Dependency: golang-bin for package: golang-1.5.1-1.el7.x86_64 --> Processing Dependency: go-srpm-macros for package: golang-1.5.1-1.el7.x86_64 --> Running transaction check ---> Package go-srpm-macros.noarch 0:2-3.el7 will be installed ---> Package golang.x86_64 0:1.5.1-1.el7 will be installed --> Processing Dependency: golang-src = 1.5.1-1.el7 for package: golang-1.5.1-1.el7.x86_64 ---> Package golang-bin.x86_64 0:1.5.1-1.el7 will be installed --> Finished Dependency Resolution Error: Package: golang-1.5.1-1.el7.x86_64 (virt7-testing) Requires: golang-src = 1.5.1-1.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [root@vm139 admin]# yum --disablerepo base --disablerepo extras --skip-broken install golang Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * updates: repo.bigstepcloud.com Resolving Dependencies --> Running transaction check ---> Package golang.x86_64 0:1.5.1-1.el7 will be installed --> Processing Dependency: golang-src = 1.5.1-1.el7 for package: golang-1.5.1-1.el7.x86_64 --> Processing Dependency: golang-bin for package: golang-1.5.1-1.el7.x86_64 --> Processing Dependency: go-srpm-macros for package: golang-1.5.1-1.el7.x86_64 --> Running transaction check ---> Package go-srpm-macros.noarch 0:2-3.el7 will be installed ---> Package golang.x86_64 0:1.5.1-1.el7 will be installed --> Processing Dependency: golang-src = 1.5.1-1.el7 for package: golang-1.5.1-1.el7.x86_64 ---> Package golang-bin.x86_64 0:1.5.1-1.el7 will be installed Packages skipped because of dependency problems: go-srpm-macros-2-3.el7.noarch from virt7-testing golang-1.5.1-1.el7.x86_64 from virt7-testing golang-bin-1.5.1-1.el7.x86_64 from virt7-testing So even with --skip-broken golang refuses to install due to requiring dependent packages.

1 0

Re: [CentOS-devel] Problem installing golang.x86_64 with virt7-docker-common-candidate
by centos-devel 30 Mar '16

30 Mar '16

Thanks for your quick responses Jan! :-) > golang.src is noarch, what about yum install golang.x86_64 golang-src.noarch? [root@vm139 admin]# yum install golang.x86_64 golang-src.noarch Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * base: mirror.ox.ac.uk * extras: mirror.cov.ukservers.com * updates: repo.bigstepcloud.com Resolving Dependencies --> Running transaction check ---> Package golang.x86_64 0:1.5.1-1.el7 will be installed --> Processing Dependency: golang-src = 1.5.1-1.el7 for package: golang-1.5.1-1.el7.x86_64 --> Processing Dependency: golang-bin for package: golang-1.5.1-1.el7.x86_64 --> Processing Dependency: go-srpm-macros for package: golang-1.5.1-1.el7.x86_64 ---> Package golang-src.noarch 0:1.4.2-9.el7 will be installed --> Running transaction check ---> Package go-srpm-macros.noarch 0:2-3.el7 will be installed ---> Package golang.x86_64 0:1.5.1-1.el7 will be installed --> Processing Dependency: golang-src = 1.5.1-1.el7 for package: golang-1.5.1-1.el7.x86_64 ---> Package golang-bin.x86_64 0:1.5.1-1.el7 will be installed --> Finished Dependency Resolution Error: Package: golang-1.5.1-1.el7.x86_64 (virt7-testing) Requires: golang-src = 1.5.1-1.el7 Available: golang-src-1.4.2-1.el7.centos.noarch (extras) golang-src = 1.4.2-1.el7.centos Installing: golang-src-1.4.2-9.el7.noarch (base) golang-src = 1.4.2-9.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [root@vm139 admin]# > Can you send me output of "rpm -qa | grep golang"? This is a freshly installed VM image cloned from an image of Centos7.2-1602 So golang is not installed yet. [root@vm139 admin]# rpm -qa | grep golang [root@vm139 admin]# [root@vm139 admin]# yum distro-sync golang golang-src Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * base: mirror.as29550.net * extras: mirror.econdc.com * updates: mirror.econdc.com No packages marked for distribution synchronization [root@vm139 admin]# many thanks, Colin

2 1

Re: [CentOS-devel] Problem installing golang.x86_64 with virt7-docker-common-candidate.
by centos-devel 30 Mar '16

30 Mar '16

Thanks Jan. As far as I can see that does not help resolve the versioning clash between the 'current' golang and the golang from virt7-docker-common-candidate Full output follows: [root@vm139 admin]# yum install golang.x86_64 golang-src.x86_64 Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * base: mirror.as29550.net * extras: mirror.econdc.com * updates: repo.bigstepcloud.com No package golang-src.x86_64 available. Resolving Dependencies --> Running transaction check ---> Package golang.x86_64 0:1.5.1-1.el7 will be installed --> Processing Dependency: golang-src = 1.5.1-1.el7 for package: golang-1.5.1-1.el7.x86_64 --> Processing Dependency: golang-bin for package: golang-1.5.1-1.el7.x86_64 --> Processing Dependency: go-srpm-macros for package: golang-1.5.1-1.el7.x86_64 --> Running transaction check ---> Package go-srpm-macros.noarch 0:2-3.el7 will be installed ---> Package golang.x86_64 0:1.5.1-1.el7 will be installed --> Processing Dependency: golang-src = 1.5.1-1.el7 for package: golang-1.5.1-1.el7.x86_64 ---> Package golang-bin.x86_64 0:1.5.1-1.el7 will be installed --> Finished Dependency Resolution Error: Package: golang-1.5.1-1.el7.x86_64 (virt7-testing) Requires: golang-src = 1.5.1-1.el7 Available: golang-src-1.4.2-1.el7.centos.noarch (extras) golang-src = 1.4.2-1.el7.centos Available: golang-src-1.4.2-9.el7.noarch (base) golang-src = 1.4.2-9.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [root@vm139 admin]# [root@vm139 admin]# yum info golang Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * base: mirror.as29550.net * extras: mirror.cov.ukservers.com * updates: repo.bigstepcloud.com Available Packages Name : golang Arch : x86_64 Version : 1.5.1 Release : 1.el7 Size : 1.1 M Repo : virt7-testing Summary : The Go Programming Language URL : http://golang.org/ Licence : BSD Description : The Go Programming Language. [root@vm139 admin]# yum info golang-src Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * base: mirror.ox.ac.uk * extras: mirror.cov.ukservers.com * updates: repo.bigstepcloud.com Available Packages Name : golang-src Arch : noarch Version : 1.4.2 Release : 9.el7 Size : 5.8 M Repo : base/7/x86_64 Summary : Golang compiler source tree URL : http://golang.org/ Licence : BSD Description : Golang compiler source tree [root@vm139 admin]#

2 1

Re: [CentOS-devel] Problem installing golang.x86_64 with virt7-docker-common-candidate.
by centos-devel 30 Mar '16

30 Mar '16

Thanks Jan. As far as I can see that does not help resolve the versioning clash between the 'current' golang and the golang from virt7-docker-common-candidate Full output follows: [root@vm139 admin]# yum install golang.x86_64 golang-src.x86_64 Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * base: mirror.as29550.net * extras: mirror.econdc.com * updates: repo.bigstepcloud.com No package golang-src.x86_64 available. Resolving Dependencies --> Running transaction check ---> Package golang.x86_64 0:1.5.1-1.el7 will be installed --> Processing Dependency: golang-src = 1.5.1-1.el7 for package: golang-1.5.1-1.el7.x86_64 --> Processing Dependency: golang-bin for package: golang-1.5.1-1.el7.x86_64 --> Processing Dependency: go-srpm-macros for package: golang-1.5.1-1.el7.x86_64 --> Running transaction check ---> Package go-srpm-macros.noarch 0:2-3.el7 will be installed ---> Package golang.x86_64 0:1.5.1-1.el7 will be installed --> Processing Dependency: golang-src = 1.5.1-1.el7 for package: golang-1.5.1-1.el7.x86_64 ---> Package golang-bin.x86_64 0:1.5.1-1.el7 will be installed --> Finished Dependency Resolution Error: Package: golang-1.5.1-1.el7.x86_64 (virt7-testing) Requires: golang-src = 1.5.1-1.el7 Available: golang-src-1.4.2-1.el7.centos.noarch (extras) golang-src = 1.4.2-1.el7.centos Available: golang-src-1.4.2-9.el7.noarch (base) golang-src = 1.4.2-9.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [root@vm139 admin]# [root@vm139 admin]# yum info golang Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * base: mirror.as29550.net * extras: mirror.cov.ukservers.com * updates: repo.bigstepcloud.com Available Packages Name : golang Arch : x86_64 Version : 1.5.1 Release : 1.el7 Size : 1.1 M Repo : virt7-testing Summary : The Go Programming Language URL : http://golang.org/ Licence : BSD Description : The Go Programming Language. [root@vm139 admin]# yum info golang-src Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * base: mirror.ox.ac.uk * extras: mirror.cov.ukservers.com * updates: repo.bigstepcloud.com Available Packages Name : golang-src Arch : noarch Version : 1.4.2 Release : 9.el7 Size : 5.8 M Repo : base/7/x86_64 Summary : Golang compiler source tree URL : http://golang.org/ Licence : BSD Description : Golang compiler source tree [root@vm139 admin]#

1 0

Problem installing golang.x86_64 with virt7-docker-common-candidate.
by centos-devel 30 Mar '16

30 Mar '16

Hi list! Apologies in advance for this has turned into a slightly long email, so I will put a short summary here at the top. I am not entirely sure if I am trying to do the right thing, so I thought it best if I were to explain clearly. TLDR: I think I need to install golang.x86_64 to make 'godeps go run' work. but yum fails with missing dependencies. Details follow. So I created a yum repo: cat << EOF > /etc/yum.repos.d/virt7-docker-common-candidate.repo [virt7-testing] name=virt7-testing baseurl=http://cbs.centos.org/repos/virt7-docker-common-candidate/x86_64/os/ gpgcheck=0 EOF I installed and configured docker-storage, docker, docker-registry. I then installed Kubernetes and managed to configure a test cluster with master and slave nodes running in VMs using CBS build from virt7-docker-common-candidate dated 10-Mar-2016 16:50 Having followed along ok with the Kubernetes 101 http://kubernetes.io/docs/user-guide/walkthrough/ and Kubernetes 201 http://kubernetes.io/docs/user-guide/walkthrough/k8s201/ I am attempting to follow along with the supplied examples. https://github.com/kubernetes/kubernetes/tree/release-1.2/examples I know very little about Go but If I am not mistaken, I need to install it to enable the k8s demos to build and function. particularly "Nginx https service" https://github.com/kubernetes/kubernetes/tree/release-1.2/examples/https-ng… The nginx-https example needs to build some certificates so a makefile calls 'godeps go run ...' error is: godep go run make_secret.go -crt /tmp/nginx.crt -key /tmp/nginx.key > /tmp/secret.json /bin/sh: godep: command not found make: *** [secret] Error 127 So I install [root@vm139 admin]# yum info godep.x86_64 Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * base: mirror.ox.ac.uk * extras: mirror.cov.ukservers.com * updates: repo.bigstepcloud.com Available Packages Name : godep Arch : x86_64 Version : 27 Release : 3.el7 Size : 1.8 M Repo : virt7-testing Summary : Dependency tool for go URL : https://github.com/tools/godep Licence : BSD Description : Dependency tool for go error is now: godep go run make_secret.go -crt /tmp/nginx.crt -key /tmp/nginx.key > /tmp/secret.json godep: No Godeps found (or in any parent directory) make: *** [secret] Error 1 ## My reading of that is that godep cannot run go because golang is not installed. ? (make_secret.go is a small file in the cwd) [root@vm139 admin]# yum info golang.x86_64 Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * base: mirror.as29550.net * extras: mirror.cov.ukservers.com * updates: repo.bigstepcloud.com Available Packages Name : golang Arch : x86_64 Version : 1.5.1 Release : 1.el7 Size : 1.1 M Repo : virt7-testing Summary : The Go Programming Language URL : http://golang.org/ Licence : BSD Description : The Go Programming Language. But am a bit stuck with getting go to function. So I attempt to install golang but this fails because of missing dependencies: Error: Package: golang-1.5.1-1.el7.x86_64 (virt7-testing) Requires: golang-src = 1.5.1-1.el7 Available: golang-src-1.4.2-1.el7.centos.noarch (extras) golang-src = 1.4.2-1.el7.centos Available: golang-src-1.4.2-9.el7.noarch (base) golang-src = 1.4.2-9.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Perhaps I am misunderstanding? Can anyone help me with this? Thanks Colin.

2 1

CentOS SCLo SIG sync-up meeting (2016-03-30)
by Honza Horak 30 Mar '16

30 Mar '16

The 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. I have no specific agenda for today, but will be at least available for discussion potential issues if anybody has something. Honza

1 1

CentOS PaaS SIG meeting (2016-03-300
by Troy Dawson 30 Mar '16

30 Mar '16

Hello, It's time for our weekly PaaS SIG sync-up meeting I don't think the meeting will be as full as last weeks, but if you want to discuss anything, this is the time. Time: 1500 UTC - Wedensdays Date: Today Wedensday, 30 March 2016 Where: IRC- Freenode - #centos-devel Agenda: - New members - Any other PaaS's wanting to join other than OpenShift? - OpenShift Current Status -- rpms - origin and it's install dependencies -- images - not started --- Next week hopefully we'll have a CentOS OSBS demo -- Quickstart - not started - Open Floor

1 0

Smoke tests for CentOS OpenShift repo
by Troy Dawson 30 Mar '16

30 Mar '16

Hi, I'm working on getting our initial CentOS OpenShift repo setup. Before I start the process of moving things out of candidate and into more official CentOS repo's, I wanted to setup a few simple tests that let me know I've got everything I need. The following repo file is for CentOS 7 machines. https://tdawson.fedorapeople.org/centos/CentOS-OpenShift.repo The only test I currently have is yum install "*origin*" Does anyone have any other simple tests, or maybe not so simple. This repo should replace the openshift-next repo on copr. Troy

2 1

Infra : changes to buildlogs.centos.org
by Fabian Arrotin 29 Mar '16

29 Mar '16

Hi, Just to let you know in advance that we'll add some modifications to the buildlogs.centos.org nodes. We got a proposal from a CDN infrastructure company (CDN77.com) willing to be a sponsor for the CentOS Project, and so we'd like to use that service for the testing/dev artifacts (so rpm packages, iso images, qcow2 images, etc) so that users can get it faster than when served from our actual buildlogs.centos.org nodes. What does that mean for you ? Next tuesday, we'll implement RewriteRule to redirect requests to those CDN backend nodes (themselves fetching/caching directly from us) The change is scheduled to be implemented on Tuesday March 29th, 8:00 am UTC time You can convert to local time with $(date -d '2016-3-29 8:00 UTC') What will be the impact ? Starting from that day, httpd will redirect you to another location for the following type of files : .rpm, .iso .qcow2{.gz,.xz}, .img{.xz} We tested that yum follows correctly the redirection, so people consuming packages from those repositories (so testing repo for the SIGs building pkgs through cbs.centos.org) will not see any impacts, except maybe an increase in available bandwidth/speed delivery (so the goal we wanted to reach) What about people downloading such images ? - browser (Firefox, Chome, others) : works directly - wget : it follows the redirection by default, so no impact - curl : if you use curl without the --location option, it will *not* follow the redirection so you'll not be able to download the needed file as before. Verify so your download scripts using curl to implement the correct options. - other method : not tested What about the integrity of the downloaded files ? - for rpm packages, you'll still get the repodata files from our nodes, meaning that only the packages will be downloaded from the cdn, and so metadata for the .rpm packages will have to match what's declared at the repodata level, ensuring integrity checks. - for the other images (.iso, .qcow2, etc) you'll be able to fetch/compare the .sha256 file for each file (or the sha256sum.txt file) from us, giving you the ability to verify also the integrity of the downloaded files. If you encounter an issue, feel free to reach us in #centos-devel. -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

3 2

devtools-4 content
by Karanbir Singh 24 Mar '16

24 Mar '16

hi guys I noticed the following rpms are not namespaced for the devtools4 scl : G: da64210f1fde669db919d3a5123b06f7a659bc6087a600b560c1e68e3ec58ccb libasan2-5.2.1-2.2.el6.x86_64.rpm G: cff6fded96723d8e6aae21f07af56cea50662113e833e31aa08c1fa8b7486403 libatomic-5.2.1-2.2.el6.x86_64.rpm G: f276242c72ef38b33e8b809ea010edd174e5b2af606d405bfe8804299be93e6a libcilkrts-5.2.1-2.2.el6.x86_64.rpm G: 2a737b3d557161090a0d4eadc0feddc9ffca773ea812006cc8b697236d0c5e2c libitm-5.2.1-2.2.el6.x86_64.rpm G: 344c1ba0767abd34c8d4c4de0cbe26397f1f7351607ab9c1314da47968ea9be9 liblsan-5.2.1-2.2.el6.x86_64.rpm G: 24799e72ae2798cade59c8c653ff5944461ea45b21e4c4da6a94fb44a66fbe7c libmpx-5.2.1-2.2.el6.x86_64.rpm G: e9cf0decfcc4a8cbb7cdaa87c38a255378c48579f30ba7c6d82608bb9257d36d libtsan-5.2.1-2.2.el6.x86_64.rpm G: 9f9fdf4e29bbc2c4ee5174c75897619c61726f18c92758b4a8d86208450a4135 libubsan-5.2.1-2.2.el6.x86_64.rpm is that by design ? regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

2 1

Audio production SIG
by Tim 23 Mar '16

23 Mar '16

Hi all, I would like to propose a new SIG for audio production. This would primarily cover to setup a digital audio workstation. I started to build some packages for this like plugins, configurations and a realtime kernel (built from git.centos.org) for a public repository. During doing all this stuff I thought of founding a SIG. I think, CentOS will be the right distribution for this, because it is really stable, reliable and long term supported. Regards Tim

7 30

Paas SIG - Proposed meeting time and agenda
by Troy Dawson 23 Mar '16

23 Mar '16

Hello, I'd like to propose a meeting time and initial agenda for the Paas SIG. Time: 1500 UTC - Wedensdays Starting this Wedensday, 23 March 2016 Agenda: - Roll Call: - Topics: -- Paas SIG members -- OpenShift rpm's -- OpenShift images -- OpenShift CentOS Quickstart - Open Floor:

3 3

CentOS SCLo SIG sync-up meeting next week (2016-03-23)
by Honza Horak 23 Mar '16

23 Mar '16

Since there seems to be a meeting collision with Config Management SIG on Wednesday, we agreed with Julien to alternate and so this week there will be Config Management SIG meeting and the SCLo SIG meeting will be held next Wednesday. However, I'd like to move the meeting time one hour earlier, so we can meet at the same time as we have always met, just in Summer time, so it 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. Honza

1 0

Vagrant image builds are failing in CBS Imagefactory
by Lalatendu Mohanty 22 Mar '16

22 Mar '16

Hi, Vagrant image builds are failing [1] [2] in CBS. I have seen similar few months back and It was some configuration issue. [1] https://cbs.centos.org/koji/taskinfo?taskID=82604 [2] https://cbs.centos.org/koji/taskinfo?taskID=82612 Thanks, Lala

2 2

getting to really minimal
by Karanbir Singh 20 Mar '16

20 Mar '16

hi I need a very very small image to get some testing work done for the cloud pieces we work on. And for this the image really needs to be as close to a just-enough set that it can boot. All I then need from there is the ability to ssh into the image, and run curl ( ie. we dont need yum and network manager and all the rest of the bits that make it a useful image ). Does anyone have a kickstart that helps get to this minimalistic point ? Regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

4 4

RPM Submission - Centos Package Cron
by Brady Wied 19 Mar '16

19 Mar '16

Homepage - https://github.com/wied03/centos-package-cron Package spec attached SRC RPM URL - https://github.com/wied03/centos-package-cron/releases/download/releases%2F… Tested against 6.6, 6.7, and 7 -- Brady Wied President *BSW Technology Consulting - *bswtechconsulting.com brady(a)bswtechconsulting.com

4 4

sclo-php5x - updates available for testing
by Remi Collet 18 Mar '16

18 Mar '16

Following packages are available in the testing repository: sclo-php56-php-pecl-http-2.5.6-1.el6 sclo-php56-php-pecl-http-2.5.6-1.el7 sclo-php55-php-pecl-http-2.5.6-1.el6 sclo-php55-php-pecl-http-2.5.6-1.el7 sclo-php54-php-pecl-http-2.5.6-1.el6 sclo-php54-php-pecl-http-2.5.6-1.el7 This fix a security issue in previous version. To install, use --enablerepo=centos-sclo-sclo-testing

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel March 2016