devel

devel@lists.centos.org

11 participants
4618 discussions

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

Update centos-art.sh script
by Alain Reguera Delgado 02 Jun '13

02 Jun '13

Hi, The centos-art.sh script was updated. This script is the tool we use to automate most frequent tasks inside The CentOS Artwork Repository. Relevant changes committed to the central repository include: * Improve rendition of logo images by using rendition configuration files instead of a SVG file. Previous to this update, the centos-art.sh script used a SVG file as model to produce the related PNG images in different formats and sizes. Combining both the CentOS symbol and the CentOS Type in a SVG file might introduce design mistakes that we want to avoid. In this commit, we remove the SVG file used to build logos and set a configuration file. This configuration file sets each component the CentOS logo is made of and using ImageMagick tools it combines the related PNG images with great precision, so we can grantee logos will always have the correct dimensions and proportions, based on their components. The configuration file also allows you to customize the image heights, formats, foreground and background colors for each image you want to produce (something previously done inside centos-art.sh script). To see how this file looks like, you can take a look at https://projects.centos.org/svn/artwork/trunk/Identity/Models/Brands/Logos/… * Add Git support for version control tasks. Previous to this commit only Subversion tasks were supported inside centos-art.sh script. In this commit, you can migrate the Subversion repository into a Git repository and perform the same version control tasks you did with Subversion, considering the differences between each system, of course. For example, if you execute the following command: centos-art locale --update Locales/Scripts/Bash --synchronize the centos-art.sh script will try to update the locale files related to centos-art.sh script and synchronize the local changes in the path provided (e.g., Locales/Scripts/Bash/) with the central repository, no matter if you are using Subversion or Git infrastructure. Notice that path arguments passed to centos-art.sh script don't include the trunk/ part on them, even when you are referring them in a trunk-branches-tags Subversion repository layout. This is something we did for compatibility reasons between Subversion repositories using a conventional trunk-branches-tags layout and Git repository layout that don't use them. By default, centos-art.sh script uses Subversion to perfrom version control tasks, however if you are trying The CentOS Artwork Repository in a Git repository, you can edit the centos-art.conf file and change the package variable from `subversion' to `git' in order to perform version control tasks using Git instead. Notice that centos-art.sh script implements Git version control tasks in order to migrate The CentOS Artwork Repository from a Subversion infrastructure to a Git infrastructure, progressively. Presently, Subversion is the official infrastructure and the one we use to share changes. You can test The CentOS Artwork Repository in your own Git infrastructure, but if you want to share changes, please, do it through Subversion infrastructure at: https://projects.centos.org/svn/artwork/. * Re-organize directory structures related to documentation manuals written in Texinfo format as illustrated in the following two figures: Figure 1. Texinfo documentation structure Documentation/Models/Texinfo/${MANUAL_NAME} `-- ${LANG} |-- ${CHAPTER_NAME}/ | `-- ${SECTION_NAME}.texinfo |-- ${CHAPTER_NAME}-menu.texinfo |-- ${CHAPTER_NAME}-nodes.texinfo |-- ${CHAPTER_NAME}.texinfo |-- Licenses -> ${TCAR_WORKDIR}/Documentation/Models/Texinfo/Default/${LANG}/Licenses |-- Licenses-menu.texinfo -> ${TCAR_WORKDIR}/Documentation/Models/Texinfo/Default/${LANG}/Licenses-menu.texinfo |-- Licenses-nodes.texinfo -> ${TCAR_WORKDIR}/Documentation/Models/Texinfo/Default/${LANG}/Licenses-nodes.texinfo |-- Licenses.texinfo -> ${TCAR_WORKDIR}/Documentation/Models/Texinfo/Default/${LANG}/Licenses.texinfo |-- ${MANUAL_NAME}.conf |-- ${MANUAL_NAME}-index.texinfo |-- ${MANUAL_NAME}-menu.texinfo |-- ${MANUAL_NAME}-nodes.texinfo `-- ${MANUAL_NAME}.texinfo Figure 2. Template for texinfo document structures Documentation/Models/Texinfo/Default/ |-- ${LANG}/ | |-- Chapters/ | | |-- section.texinfo | | `-- section-functions.texinfo | |-- Chapters-menu.texinfo | |-- Chapters-nodes.texinfo | |-- Chapters.texinfo | |-- Licenses/ | | |-- GFDL.texinfo | | `-- GPL.texinfo | |-- Licenses-menu.texinfo | |-- Licenses-nodes.texinfo | |-- Licenses.texinfo | |-- manual-index.texinfo | |-- manual-init.pl | |-- manual-menu.texinfo | |-- manual-nodes.texinfo | |-- manual.conf | |-- manual.sed | `-- manual.texinfo |-- manual-init.pl `-- manual.sed The details of all these and minor changes not shown here are available at: https://projects.centos.org/trac/artwork/timeline All suggestions and comments are very welcome. You can send e-mails to this list or fill tickets at https://projects.centos.org/trac/artwork/newticket. Best regards, -- Alain Reguera Delgado <alain.reguera(a)gmail.com>

1 0

Update wiki theme - Round 2
by Alain Reguera Delgado 01 Jun '13

01 Jun '13

Hi, There are a few more updates available for our wiki theme in the https://projects.centos.org/svn/artwork/trunk/Identity/Webenv/Themes/Defaul… location. These changes try to be consequent with the current wiki design on-line, with the following additions: - Identity/Webenv/Themes/Default/Moin/1.5.9/Modern.py: Update position of search form and page title. The search form was moved from the heading top-right corner to the page content top-right side. The search form isn't visible when you are editing a page. The page title was added to page content top-left side. In the same visual line where search form is placed in. Here page title controls the way search form is displayed. The page title is displayed as a block, while the search form is floating on its right. - Identity/Webenv/Themes/Default/Moin/1.5.9/Modern/css/common.css: Don't make form element to display in line. This may create distortions when forms are shown inside lists (e.g., ul, li, etc.). Don't force all hr to be 1px height. There are hr1, hr2 ... hr6 classes which purpose is control the horizontal rule height. Make borders 3px rounded to pre elements. - Identity/Webenv/Themes/Default/Moin/1.5.9/Modern/css/screen.css: Make user name margin 0 with the intention of saving space on top of it. Add some space (5px) between the search form and the edit bar elements. This way, the search form seems to be aligned with the page title on its left. The `-moz-border-radius' property is 3px now. Reset the page trail style to fit the previous look on heading. Make page location 5px of both top margin and bottom margin. This helps to keep both page title and search form horizontally aligned one another. Add visual styles to reflect the fact that hr1..hr6 does exist. Make borders 3px rounded to h1, h2 and div.table-of-contents elements. Also, close the table of content's title by adding a bottom border to it. - Identity/Webenv/Themes/Default/Moin/1.5.9/RecentChanges.png: Update image to reflect changes described above. I would appreciate any comment from you. Best regards, -- Alain Reguera Delgado <alain.reguera(a)gmail.com>

1 0

Add clamav rpm to extras or contrib ??
by Ben Mohilef 24 May '13

24 May '13

There was a security update to clamav on 4/23/2013. RPM'S for this widely used antivirus used to be maintained in rpmforge, but they have no current updates in their repo for centos-5. Could this be added to either centos extras or centos contrib and maintained by someone on the centos team ? The rpm rebuild is pretty simple and takes a short amount of time and resource

2 1

Update wiki theme artworks
by Alain Reguera Delgado 24 May '13

24 May '13

Hi guys, It has been a long time since the last time we talked about CentOS artworks. So, it is time to throw some woods into the fire :). We have some theme updates for our wiki in the following location: https://projects.centos.org/svn/artwork/trunk/Identity/Webenv/Themes/Defaul… I'm wondering if it would be possible for someone to install this updates in a public test server where the community can test it and report their impressions. The relevant changes in this commit are: - Update brand information. The brand information used in the wiki was modified to fit the colors used by the CentOS symbols inside the CentOS distribution. There are small color differences between them and that is something we need to avoid. It is very important that brand information be exactly the same in all visual manifestations. The brand I present now for the wiki is a combination of "The CentOS Logo" followed by a "semitransparent-dotted horizontal bar" and the word "Wiki" next to it. This proportion seems to be well balanced and I would propose it for using in the CentOS websites. Inside this brand information, "The CentOS Logo" and the "semitransparent-dotted horizontal bar" do not change. The "Wiki" word can change to reflect other areas (e.g., Projects, People, Bugs, Blog, etc.). - Update admonitions visual style. The admonition visual style used in the wiki was modified based on DocBook XHTML output. Icons were also updated so the whole artwork result being more attractive and consistent. - The style related to tabs was revised and improved. Now tabs both upside and downside the page have rounded corners when you use firefox as web browser. - The trail of pages was moved from heading to page content. This way, heading will always have the same height, no matter if page trails are active or not. - No banner for external promotions visible. - Update heading background. Now it is an array of small blue circles. This background is the same we use in DocBook documentation. - Update content of RecentChanges page. Use admonitions in the hint section, remove left margin from tables, and remove extra space on images and icons shown inside recent changes tables. To show such changes, we add RecentChanges.png and RecentChanges.txt files. If you want your RecentChanges page to look like this, you need to edit the one you have on your wiki and replace its content with that in RecentChanges.txt instead. Best Regards, -- Alain Reguera Delgado <alain.reguera(a)gmail.com>

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