devel

devel@lists.centos.org

10 participants
4625 discussions

IanNicholson
by Nicholson, Ian 09 Nov '16

09 Nov '16

Hi. I want to get involved in your community. I am in university and have an assignment to get involved with an open source software initiative. As I am already using centOS it makes sense to get involved. Is there a page with all bugs etc listed that I can use? I am running centOS on a version of oracles vm and have this on a Windows 10 platform. Can I request a Web page also please. I look forward to working together. Regards Ian Nicholson.

1 0

Update on status of CentOS Community Container Pipeline
by Bamacharan Kundu 09 Nov '16

09 Nov '16

Hi, Here is the update in for the work done recently, for the CentOS Community Container Pipeline. * Atomic registry container images got through container pipeline and now available in registry.centos.org * Cockpit-kubernetes and cockpit-ws got delivered to registry.centos.org from centos distro components. * Openshift-origin is delivered with version 1.2.1, 1.3.1 and 1.3.1 as latest. * We have updated the notification email bodies to get with proper contents. Along with subjects mentioning proper state of the builds with logs. * Results from multiple scanners are now consolidated to single mail so that the user gets only one mail with all the required details. In the coming days, we will be focusing on: * Containerizing the workers to for resolving conflicts in writing the configs by multiple workers. * Triggering docker linter before each of the builds so that we can notify user about problems in target file to be built and have a quick feed back. * Make the workers stateless and fault tolerant to handle repeating and unfinished jobs. Regards Bamacharan Kundu

1 0

contributions to opstools and notification of changes
by Matthias Runge 08 Nov '16

08 Nov '16

Hello, we're moving forward with enabling contributions to opstools. As you probably know, the repositories live on Github[1] Over the next few days/weeks, we'd move for submissions from pull requests to using a gerrit based setup hosted here [2] Now the question: we can have an irc bot notifying on new patches; would it be considered to noisy/unfriendly to get the notifications on #centos-devel ? Should we create an own channel? Thanks, Matthias [1] https://github.com/centos-opstools [2] https://review.rdoproject.org/r/#/q/status:open

1 0

Re: [CentOS-devel] ATTN: OCaml 4.04 in Rawhide, could affect POWER, s/390, RHEL 7.4, CentOS 7.4
by Richard W.M. Jones 08 Nov '16

08 Nov '16

On Tue, Nov 08, 2016 at 09:11:01AM +0000, Peter Robinson wrote: > OK, well just update the rel-eng ticket when you want it merged back > into rawhide. This will hopefully be later today or tomorrow. I've got a few packages that I'm still debugging. Will update the ticket when ready. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v

1 0

ATTN: OCaml 4.03 in Rawhide, could affect POWER, s/390, RHEL 7.4, CentOS 7.4
by Richard W.M. Jones 08 Nov '16

08 Nov '16

OCaml 4.03 has been out for a while. I'm intending to add it to Fedora Rawhide once a side tag has been created: https://fedorahosted.org/rel-eng/ticket/6486 This will require rebuilding every OCaml package, which I normally do using a script, but probably there will be manual rebuilds necessary too. A few issues that may affect people: (1) There is a new ppc backend upstream, and I intend to switch to this. For years we have maintained our own out-of-tree ppc64 & ppc64le backends. I want to switch to the upstream ppc backend (which supports, in theory, ppc 32 bit, ppc64 and ppc64le). However when I actually tried this I found it to be rather buggy, it couldn't even compile many basic OCaml packages. This time I intend to switch, and we'll deal with the bugs. (2) There is a new s/390x backend upstream. This should enable us to compile all s/390x packages as native code. It also means that all supported architectures (yes, even riscv64) will support native compilation for OCaml. (3) The real reason I'm doing this now is because partners have asked us to update the OCaml compiler in RHEL 7.4. This will be a binary ABI break -- it's unfortunately unavoidable -- and will require all OCaml-using programs to be recompiled, and of course that will affect CentOS and any other RHEL derivatives. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org

2 3

Re: [CentOS-devel] RPM naming conventions for upstream
by Thomas F Herbert 08 Nov '16

08 Nov '16

On 11/07/2016 02:36 AM, Karanbir Singh wrote: > On 7 November 2016 02:13:05 GMT+00:00, Thomas F Herbert > <therbert(a)redhat.com> wrote: > > Folks, > > I have code to build DPDK RPM's built for 16.07 release merged > upstream in new dpdk-rpm project we started in fd.io. I also > modified the vpp rpm creation so it was more distro friendly, so > it could be built from a dist tarball or a SRPM. > > My questions are about RPM naming conventions for Centos for DPDK, > vpp and other upstream NFV related projects to come. > > I built RPMs previously for OVS/DPDK and DPDK in OPNFV and stuck > pretty to the Fedora naming conventions and nobody complained. But > somehow, I don't think that what I have done so far will meet the > more strict standards of the DISTRO. > > To begin with, could you please point me to some guidelines for > file names. I see them for Fedora everywhere but I am fuzzy on > what would be required for Centos. > > In order for the changelog to be meaningful it seems that there > should be a git hash tag appended to file name. however, when the > RPM is an unaltered "pure" upstream release with no patches I am > not sure this is necessary. > > Forgive me if these seem like stupid questions but I am trying to > get a few bits together upstream and then I should be able to > start building in Koji for the NFV SIG and I want to make sure I > do things "right!" > > --Tom > > > -- > *Thomas F Herbert* > SDN Group > Office of Technology > *Red Hat* > > > Hi Thomas > > We rely on the Fedora naming and packaging guidelines. If you are > aligned with their specifications - you should be all set on our side too. Please double check: Here is the built 16.07 dpdk RPM built in fd.io: https://nexus.fd.io/content/repositories/fd.io.master.centos7/io/fd/rpm_dpd… I am not sure the ".0" should be there? > > Regards > -- > Sent on the move, excuse my typos -- *Thomas F Herbert* SDN Group Office of Technology *Red Hat*

1 0

CentOS Storage SIG meeting on Friday 28-Oct-2016 at 13:00 UTC
by Niels de Vos 07 Nov '16

07 Nov '16

Hi all, We did not have a Storage SIG meeting for a while. Now we have interest from additional participants to join the SIG, so it would be good to have a chat again. The (old) time that was used did not seem practical for most attendees, so tomorrow we're planning to have the meeting a little earlier, namely at 13:00 UTC. run "date -d '13:00 UTC'" in your terminal to convert to $LOCALTIME The venue will be #centos-devel on Freenode :) The agenda will mostly be done ad-hoc, with at least the following topics: - roll call - current state of Ceph packaging and testing - current state of Gluster packaging and testing - plans for Samba inclusion - plans for Tendrl inclusion - any other business Thanks, Niels

2 2

[scl.org] [SCLo SIG] new sclo-php70-* packages available for testing
by Remi Collet 07 Nov '16

07 Nov '16

Available in centos-sclo-sclo-testing * sclo-php70-php-pecl-apcu * sclo-php70-php-pecl-apfd * sclo-php70-php-pecl-http * sclo-php70-php-pecl-mongodb * sclo-php70-php-pecl-propro * sclo-php70-php-pecl-raphf * sclo-php70-php-pecl-uploadprogress * sclo-php70-php-pecl-xdebug These packages provide additional extensions for the new rh-php70 collection available in centos-sclo-rh-testing More packages will come later, according to user requests. Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo

1 0

[SCLo SIG] new sclo-php56-php-pecl-mongodb packages available for testing
by Remi Collet 04 Nov '16

04 Nov '16

Available in centos-sclo-sclo-testing * sclo-php56-php-pecl-mongodb This new extension allow to work with MondoDB server https://pecl.php.net/package/mongodb The old "mongo" extension is considered as deprecated, and will not be adpated for PHP 7. The new "mongodb" extension is recommended for new project, and is already compatible with PHP 5 and 7. Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo _______________________________________________ CentOS-devel mailing list CentOS-devel(a)centos.org https://lists.centos.org/mailman/listinfo/centos-devel

1 0

[SCLo SIG] new rh-php* packages available for testing
by Remi Collet 04 Nov '16

04 Nov '16

Available in centos-sclo-rh-testing * rh-php56 collection have been updated to PHP 5.6.25 * rh-php70 new collection, provides PHP 7.0.10 These packages are the same that in RHSCL 2.3.0-beta. http://developers.redhat.com/blog/2016/10/20/red-hat-software-collections-2… Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel