devel June 2013

devel@lists.centos.org

16 participants
12 discussions

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

initial testing version for DevTools 1.1
by Tru Huynh 16 Aug '13

16 Aug '13

Hi, For the daring users ;) http://people.centos.org/tru/devtools-1.1/ enjoy and report Cheers, Tru -- Tru Huynh (mirrors, CentOS i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

5 26

Re: [CentOS-devel] [CentOS] OT: About rebuilding RHS and RHEV
by C. L. Martinez 28 Jun '13

28 Jun '13

On Fri, Jun 28, 2013 at 7:51 AM, Baptiste AGASSE <baptiste.agasse(a)lyra-network.com> wrote: > Hi, > > I tried to rebuild JBoss EAP 6.0.1 (which was used bay RHEV engine) and RHEV 3.1 from SRPMs some months ago without success (missing some dependencies). I used mock. A week ago I've successfuly built JBoss EAP 6.1 Final from sources (with some little changes because Redhat don't publish some maven plugins and dependencies like slf4j, byteman, hibernate3, junit). > > Have a nice day. > > Regards. > > --- > Baptiste > Thanks Baptiste. After reading docs about RHEV, I have discarded (rebuilding RHEV and RHEM is too much). But not RedHat Storage Server. Reading about it, I see it is based in RHEL EUS 6.2.z and not RHEL 6.4 as I had been assumed. I have located the updates that RedHat has released for RHEL 6.2.z since Centos ceased to publish patches for 6.2 release. My question: If I not wrong, mock uses jails or chroot environments to rebuild packages. Can I use a CentOS 6.4 x86_64 host to rebuild all patches released by RedHat for RHEL 6.2.z and Storage Server 2.0 without problems?? Does someone has tested? P.D: Sorry for the cross posting to centos-devel, but maybe it is an interesting question to publish in centos-devel list.

2 3

tcl8.6 build fails
by Jens Neu 28 Jun '13

28 Jun '13

Dear list, I'm trying to build tcl8.6.0 which some developers want/need. Took the spec file from srpm, and updated to 8.6 as such: http://paste.debian.net/12932/ What I did: - updated version to 8.6.0 - disabled sdt - disabled patches for 5.8.x - changed configure options (s/disable-threads/enable-threads/) and gave it a try. it builds fine, works as far as %install, does the "for i in *.h" (line 104) and gives me a RPM build errors: Bad exit status from /var/tmp/rpm-tmp.Fxgmu1 (%install) now, what puzzles me: 1) the exit status does not give me a line or something what failed 2) the rpm-tmp.Fxgmu1 looks good from inspection 3) sh -x /var/tmp/rpm-tmp.Fxgmu1 runs happily and performs as expected. 4) rpmbuild -vv does not give any more clues as without. ideas anyone how to debug further? best regards Jens www.biotronik.com BIOTRONIK - Celebrating 50 years of excellence Founded in 1963 with the development of the first German pacemaker, BIOTRONIK has brought innovations and the highest quality standards to the cardiac rhythm management and vascular intervention fields in more than 100 countries around the world. We’ve developed advanced technologies such as BIOTRONIK Home Monitoring®, Closed Loop Stimulation (CLS) and Orsiro, the industry's first hybrid drug eluting stent. BIOTRONIK also offers the broadest portfolio of cardiac devices with ProMRI®, an advanced technology that gives patients access to magnetic resonance (MR) scanning. BIOTRONIK SE & Co. KG Woermannkehre 1, 12359 Berlin, Germany Sitz der Gesellschaft: Berlin, Registergericht: Berlin HRA 6501 Vertreten durch ihre Komplementärin: BIOTRONIK MT SE Sitz der Gesellschaft: Berlin, Registergericht: Berlin HRB 118866 B Geschäftsführende Direktoren: Christoph Böhmer, Dr. Lothar Krings This e-mail and the information it contains including attachments are confidential and meant only for use by the intended recipient(s); disclosure or copying is strictly prohibited. If you are not addressed, but in the possession of this e-mail, please notify the sender immediately and delete the document.

4 13

sos reports configured to send to redhat
by John Newbigin 26 Jun '13

26 Jun '13

Hi, I am looking at configuring sosreport on CentOS-6.4 and I was surprised to see the following config file: /etc/sos.conf: [general] ftp_upload_url = ftp://dropbox.redhat.com/incoming gpg_keyring = /usr/share/sos/rhsupport.pub gpg_recipient = support(a)redhat.com ... I don't know if those settings are being used but perhaps there should be a CentOS config or at least have these values stripped out. My reports are emailed to root. I am yet to work out the real configuration of sos/abrt. John. -- John Newbigin | ITS Senior Analyst / Programmer Faculty of Information and Communication Technologies ITS | Swinburne University of Technology | Melbourne, Australia O: EN306 | T: +61 3 9214 8185 | M: +61 410 569 362 E: jnewbigin(a)swin.edu.au W: http://www.ict.swin.edu.au/staff/jnewbigin

3 2

How to rebuild the Centos 6.4 iso images with the same contents as officially released iso images ?
by Martin Robrecht 18 Jun '13

18 Jun '13

I have read many Centos webpages and mail archives but found only raw descriptions of the build process. My first aim is to rebuild CentOS-6.4-x86_64-LiveCD.iso using the Centos repositories and preferably without recompiling the SRPMs, just to verify the build process. My final aim is to create a Centos LiveOS contain the packages in CentOS-6.4-x86_64-minimal.iso plus some network configuration changes and some own executables preinstalled. --- Only background, not part of the question --- I tried to build a LiveOS on Centos6.4 x86_64 host using livecd-creator ( livecd-tools-13.4-2.el6.x86_64 ): LANG=C livecd-creator --config=centos-livecd-minimal.ks –fslabel=CentOS-minimal centos-livecd-minimal.ks ( adapted from https://projects.centos.org/trac/livecd/browser/trunk/CentOS5/centos-livecd… ) : lang en_US.UTF-8 keyboard us timezone US/Eastern auth --useshadow --enablemd5 selinux --enforcing firewall --disabled repo --name=a-base --baseurl=http://mirror.centos.org/centos/6.4/os/x86_64 repo --name=a-updates --baseurl=http://mirror.centos.org/centos/6.4/updates/x86_64 #repo --name=a-extras --baseurl=http://mirror.centos.org/centos/6.4/extras/x86_64 repo --name=a-live --baseurl=http://www.nanotechnologies.qc.ca/propos/linux/centos-live/x86_64/live %packages bash kernel syslinux passwd policycoreutils chkconfig authconfig rootfiles comps-extras xkeyboard-config %end The generated .iso File fails to boot on a real and on a VirtualBox machine with a problem in the initial ramdisk : dracut: Fatal: Don't know how to handle 'root=live:UUID=a68d794a-d777-4e4f-86ba-d2cc50d8fa1e' dracut: Refusing to continue Kernel panic – not syncing : Attempted to kill init

1 0

CentOS build/repo of MRG Realtime
by Lissade, Joel 12 Jun '13

12 Jun '13

We are interested in using CentOS 6.x with the MRG Realtime kernel. Are there any plans in providing a CentOS repository for the MRG packages? I was able to install the MRG realtime package from Scientific Linux distribution on top of CentOS 6.2 and run, but we would prefer to install from the CentOS repository. Thanks for any info, -Joel

3 6

Corosync/Pacemaker mess after upgrade to 6.4
by France 11 Jun '13

11 Jun '13

Hi all, i've been using Corosync (with Pacemaker) for my production HA iscsi service. Upon upgrading to CentOS 6.4, the upgraded node will not join the cluster. It might also be a bug within pacemaker code, but i'm not sure. There is also crm command missing (i know i can get in from suse repo). I saw the RH's 6.4 technical notes: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux… where they suggest we move to cman. Because the upgrade brakes working cluster with corosync/pacemaker setup, i would like to propose, that we add this into to release notes for CentOS 6.4. I'm also thinking about the best way to get fully working cluster back. All suggestions are welcome. Please note that we must not stop currently running resources. Is it possible, that there is a bug in new pacemaker (1.1.8-7.el6) and it won't work with old pacemaker (1.1.7-6.el6) or are they just incompatible be default? (Nodes after upgrade don't see each other.) I also wonder, will corosync be removed in future RH 6.* releases and should i move over to cman? Regards, F.

1 0

Unsigned package
by Shad L. Lords 07 Jun '13

07 Jun '13

The 6.4/updates/Source/SPackages/selinux-policy-3.7.19-195.el6_4.3.src.rpm on vault isn't signed.

2 1

The CentOS Artwork Repository - Next steps
by Alain Reguera Delgado 02 Jun '13

02 Jun '13

Hi, In case there is not other plan, the immediate development plan for The CentOS Artwork Repository will be addressed to share specific repository components (e.g., automation scripts) with other projects that use the same directory structure The CentOS Artwork Repository does. Let me put a real example. I've been working on a project named solinfo-network. This project documents a local network I'm creating to share The CentOS Artwork Repository development with friends that don't have Internet access, but a computer, a modem and a fixed telephone line only. While I was organizing this project, I found that most of my structuring needs were nicely solved by using the same structure The CentOS Artwork Repository has. So I created a Git repository for it and duplicate the same structure of The CentOS Artwork Repository. At this point, I ended up with two different repositories and two different automation scripts trees. So, reading the progit-book I found that using submodules it is possible to put one project inside another so specific components' development could be shared instead of duplicated. In order to achieve this, it is necessary to re-organize some components inside the repository and create a new repository for automation scripts, the component we want to share. For example, the following idea is being studied: --------------------------------------------------------- ssh://gitolite@projects.centos.org:centos-artwork --------------------------------------------------------- Identity/ (LOCAL SUBTREE) |-- Images/ | |-- Documentation/ | | `-- ${LANG}/ | |-- Brands/ | |-- Icons/ | |-- Themes/ | | `-- ${THEME_NAME}/ | | `-- ${THEME_VERSION}/ | | |-- Concept/ | | |-- Backgrounds/ | | |-- Media/ | | |-- Posters/ | | |-- Palettes/ | | `-- Distro/ | | `-- ${DISTRO_RELEASE}/ | | `-- ${DISTRO_COMPONENT}/ | | `-- ${LANG}/ | `-- Webenv/ |-- Models/ | |-- Documentation/ | |-- Brands/ | |-- Icons/ | |-- Themes/ | | `-- Default/ | | |-- Concept/ | | |-- Media/ | | |-- Posters/ | | |-- Palettes/ | | `-- Distro/ | | `-- ${DISTRO_RELEASE}/ | | `-- ${DISTRO_COMPONENT}/ | `-- Webenv/ Documentation/ (LOCAL SUBTREE) |-- Manuals/ | |-- Texinfo/ | | `-- ${MANUAL_NAME}/ | | `-- ${LANG}/ | |-- Docbook/ | | `-- ${MANUAL_NAME}/ | | `-- ${LANG}/ | `-- Latex/ | `-- ${MANUAL_NAME}/ | `-- ${LANG}/ |-- Models/ | |-- Texinfo/ | | `-- ${MANUAL_NAME}/ | |-- Docbook/ | | `-- ${MANUAL_NAME}/ | `-- Latex/ | `-- ${MANUAL_NAME}/ Locales/ |-- Identity/ | `-- Models/ | |-- Documentation/ | | `-- ${LANG}/ | |-- Brands/ | |-- Icons/ | |-- Themes/ | | `-- Default/ | | |-- Concept/ | | | `-- ${LANG}/ | | |-- Media/ | | | `-- ${LANG}/ | | |-- Posters/ | | | `-- ${LANG}/ | | `-- Distro/ | | `-- ${DISTRO_RELEASE}/ | | `-- ${DISTRO_COMPONENT}/ | | `-- ${LANG}/ | `-- Webenv/ |-- Documentation/ | `--Models/ | |-- Texinfo/ | | `-- ${MANUAL_NAME}/ | | `-- ${LANG}/ | |-- Docbook/ | | `-- ${MANUAL_NAME}/ | | `-- ${LANG}/ | `-- Latex/ | `-- ${MANUAL_NAME}/ | `-- ${LANG}/ Scripts/ (REMOTE SUBTREE) --------------------------------------------------------- ssh://gitolite@projects.centos.org:centos-artwork-scripts --------------------------------------------------------- / |-- Functions/ | |-- Commons/ | |-- Help/ | |-- Render/ | |-- Locale/ | |-- Vcs/ | |-- Tuneup/ | `-- Prepare/ |-- Documentation/ | |-- Manuals/ | | `-- ${LANG}/ | | |-- centos-art-render.man | | |-- centos-art-help.man | | |-- centos-art.man | | |-- centos-art.xhtml | | |-- centos-art-xhtml/ | | `-- centos-art.pdf | `-- Models/ | |-- centos-art-render.Docbook | |-- centos-art-help.Docbook | `-- centos-art.Docbook |-- Locales/ | |-- Functions/ | | `-- ${LANG}/ | | |-- centos-art.sh.po | | |-- centos-art.sh.pot | | `-- LC_MESSAGES | | `-- centos-art.sh.mo | `-- Documentation/ | `-- Models/ | `-- ${LANG}/ | |-- centos-art-render.po | |-- centos-art-help.po | `-- centos-art.po |-- centos-art.sh `-- centos-art.conf Once this has been done, other areas in which I plan to work on include: * Changing Docbook physical divisions from using entities to using Xinclude instead. This includes to update the centos-art.sh script to do the appropriate production of different output formats and documentation management. * Separate production tasks from management tasks. For example, the help functionality is taking care of producing output formats for Texinfo formats while the render functionality is taking care of producing output formats for Docbook formats. I think the help functionality should take care of all management tasks (e.g., create, edit, delete, documentation manuals in different formats) and the render functionality should take care of producing output formats for both Texinfo and Docbook. * Implement Docbook format inside help functionality. Presently only Texinfo is supported. * Write documentation related to centos-art.sh script and all its functions. This is my list of things to do for the next months. I do appreciate any comment or suggestion you could post about it. Any help you could give in these directions will be very much appreciated, as well. As more community involvement we have the better focused our work will be. I probably ought to begin these e-mails by asking you for excuses because of my long time off-line, intermittent presence on the mailing list and sometimes unfocused behavior. I've been having issues to find a job that let me purchase Internet access and left me time to get more involved in the project. I am very glad to tell you that after months of hard working, I have an entire month and 10 hours of Internet access, to fully spend with you guys! :) I want to thank you all for the magnificent work you are doing, and all the kindness you've put on it through time. Best regards, -- Alain Reguera Delgado <alain.reguera(a)gmail.com>

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel June 2013