devel

devel@lists.centos.org

4 participants
4696 discussions

How can I get the bash configure options?
by Lookey Lam 08 Sep '09

08 Sep '09

Hello: I am now using the bash-4.0 source code to complie my own binary package. And I would like to make sure it is compatible with CentOS-5.2's bash. How can I get the compiler options release by centOS official. Thanks. lookey

2 1

Apache ServerTokens says Red Hat
by Peter Magnusson 06 Sep '09

06 Sep '09

Hey. I was quite annoyed by the fact that one of my fully updated CentOS 5.3 boxes said "Red Hat" instead of CentOS when listing an empty dir with apache like this: http://flashdance.cx/tmp/ (said CentOS before) and http://www.flashdance.cx/tmp/ that said Red Hat. Talked with some guys in #centos irc and alot of stuff was tested to see why it differ. Then I realized that the one that still said CentOS hasnt been restarted since the box was rebooted, Jun16: root 4747 0.0 0.1 17468 4836 ? Ss Jun16 0:01 /usr/sbin/httpd thats why it still said CentOS! After restart of apache, it says Red Hat. Now I dont have the previous httpd rpm file but I guess it happend with httpd-2.2.3-22.el5.centos.2 that I have installed now, ServerTokens isnt changed to CentOS in it. It needs to be fixed :)

10 20

Links our Mantis to upstreams' Bugzilla - a idea for the community to help with
by Tim Verhoeven 02 Sep '09

02 Sep '09

Hi, I would like the send out the mail below to centos-devel (probably, seems the best place). The idea is that when we need to monitor a upstream bug we could just enter the upstream bugzilla number into mantis and that from then on any updates made in the bugzilla report would also be added to our bugreport. That makes it much easier to track upstream bugreports. I've googled around and I could not find anything that already does such a thing. Here is the mail : Hello, We have a project for which we are could use some help. Its about creating a link between our Mantis bugtracker (bugs.centos.org) and upstreams Bugzilla (bugzilla.redhat.com) At the moment we need to manually track all upstreams bugs reported in our own bugtracker. This is a time-consuming process and it something that can be automated. So why not do it. My idea was to create a daemon of some sort that at regular intervals checks all bugs in our systems that have a upstream bugzilla number entered (Mantis support customs fields that could be used for this). If there is a update in the bugzilla since the last run it is copied into the bug in Mantis. That why we can get notified automatically and can react to the updates more quickly and spend less time needing to follow up. Well, this is just my idea on how to implement it. If there are others suggestions, please let me know. Also, I've googled to find if something like this already existed but I could not find anything. So, who has some scripting experience (the language doesn't matter) that wants to have a go at this ? Thanks, Tim -- Tim Verhoeven - tim.verhoeven.be(a)gmail.com - 0479 / 88 11 83 Hoping the problem magically goes away by ignoring it is the "microsoft approach to programming" and should never be allowed. (Linus Torvalds)

3 5

shm & rtkaio conflict
by Eyal David 01 Sep '09

01 Sep '09

Hello, I'm trying to implement an application using shared memory. The shm_open and shm_unlink functions specify in the man page that they should be linked with the -lrt flag. However, my application also uses the rtkaio support so I link with the -lrtkaio. When I try to link without -lrt I get: relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object And when I link with -lrt (and without -lrtkaio) I break my application. Any suggestions about how to solve this issue? Thank you, eyal

1 0

old packages in centos-base repo after upgrade to 4.8
by Nikola Ciprich 25 Aug '09

25 Aug '09

Hello, it seems there is something wrong with the repositories after 4.8 release. some packages (pango, acpid and most notably bind, probably others too) are in much older versions in base repo then they were in updates before 4.8 Could somebody check it please? with best regards nik -- ------------------------------------- Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: servis(a)linuxbox.cz -------------------------------------

3 8

functional testing as a contrib requirement
by Karanbir Singh 14 Aug '09

14 Aug '09

As a part of the contrib acceptance process, can we spread the load a bit by saying that anyone who wants to submit a package, must also find someone else ( other than their sponsor ) to write a set of acceptance tests[1] for their package. I realise that in some cases, its going to be non-trivial writing these sort of tests, eg when looking at a new kernel module that needs specific hardware to be present for it to do something testable. However in many cases its really very trivial ( eg. writing tests for bind are extremely easy, just need to get a set of configs into place and run a dns lookup or a dozen ). How I imagine this to work would be that a post-build testing harness could do whatever environment/teardown is required, get a clean instance installed, get the fresh packages into there and run the tests. Stage1 could be just a standard test harness that ensures the quality of the rpms being built and how they work as a collection, tools like repomanage etc could be part of Stage1. Follow that up with the acceptance tests written specifically for the package. Dont care what testing framework is used, even bash will work in most cases ( shunit2 ? ), simpletest, rspec, python-unit. Whatever. As long as it can be called from the command line, it should work. Just wanted to get the idea out there and see what the general feeling is about this. If people are seriously keen, we cn even rip out unit and integration tests from inside package %build sections and run them post-install :) Although as something to start with, lets not go that far. [1]: http://en.wikipedia.org/wiki/Acceptance_testing -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

4 7

iSCSI Enterprise Target
by Ross Walker 14 Aug '09

14 Aug '09

I was wondering if there was room in 'extras' for IET? If there is interest let me know and I can supply/maintain the packages. Just need to modify them to track kernel API. -Ross

5 12

Re: [CentOS-devel] [CentOS-announce] CESA-2009:1193 Important CentOS 5 x86_64 kernel Update
by Phil Schaffner 11 Aug '09

11 Aug '09

Karanbir Singh wrote: > CentOS Errata and Security Advisory 2009:1193 Important > > Upstream details at : https://rhn.redhat.com/errata/RHSA-2009-1193.html > > The following updated files have been uploaded and are currently > syncing to the mirrors: ( md5sum Filename ) > > x86_64: > 38f5887b9822006c68b4486716ae18d1 kernel-2.6.18-128.4.1.el5.x86_64.rpm > aa0c5bb5e7b4eecde44018cd95e9ea28 kernel-debug-2.6.18-128.4.1.el5.x86_64.rpm > f62dd4c14d4911d3161a7e8574d43da0 kernel-debug-devel-2.6.18-128.4.1.el5.x86_64.rpm > 8aac2fdf2312fde27f09c99d739d617c kernel-devel-2.6.18-128.4.1.el5.x86_64.rpm > 64e37705920db6068c982a0d004fd318 kernel-doc-2.6.18-128.4.1.el5.noarch.rpm > b80d5df60492256a43f9a799ae97b9f5 kernel-headers-2.6.18-128.4.1.el5.x86_64.rpm > 384fa34172a633669e7738c09542e543 kernel-xen-2.6.18-128.4.1.el5.x86_64.rpm > eab0550cbdecd1722a8fd0530a0ca1f5 kernel-xen-devel-2.6.18-128.4.1.el5.x86_64.rpm > > Source: > 4e72b5e4b6d676f21be6d0164e6c31c6 kernel-2.6.18-128.4.1.el5.src.rpm > Should kernel-debug be installed as a dependency if it was not previously installed? A "yum update" now wants to install kernel-debug. Phil

4 4

[CentOS-devel] http://www.centos.org/modules/smartfaq/faq.php?faqid=21
by John Summerfield 11 Aug '09

11 Aug '09

WBEL isn't at the location mentioned. -- Cheers John -- spambait 1aaaaaaa(a)coco.merseine.nu Z1aaaaaaa(a)coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-)

1 0

ELrepo video4linux on CentOS 5 2.6.18-128.4.1.el5xen - can't work !
by Philippe 08 Aug '09

08 Aug '09

hello, I'm running on centos5.3 xen [root@aberlour]# uname -a Linux aberlour 2.6.18-128.4.1.el5xen #1 SMP Tue Aug 4 21:33:24 EDT 2009 i686 athlon i386 GNU/Linux I installed elrepo to use my webcam(S). the package kmod-video4linux-xen is really installed: [root@aberlour]# rpm -qa|grep video kmod-video4linux-xen-0.0-5.20090615.el5.elrepo but when I "modprobe gspca_main" I've got. [root@aberlour]# modprobe gspca_main FATAL: Module gspca_main not found. the problem is that the module is located in the wrong directory [root@aberlour]# locate gspca_main.ko /lib/modules/2.6.18-128.el5xen/extra/video4linux/gspca_main.ko instead of: /lib/modules/2.6.18-128_.4.1._el5xen/extra/video4linux/gspca_main.ko I tried to link /lib/modules/2.6.18-128_.4.1._el5xen/extra to /lib/modules/2.6.18-128.el5xen/extra and run a depmod. But I got an error message [root@aberlour]# modprobe gspca_main FATAL: Error inserting gspca_main (/lib/modules/2.6.18-128.4.1.el5xen/extra/video4linux/gspca_main.ko): Invalid module format after having discussion (and many tests) with Phil Perry (from ELrepo) the conclusion is that their module is not compatible with CentOS XEN All the posts are here: http://lists.elrepo.org/pipermail/elrepo/2009-August/date.html#23 Can someone help ? how can I use a gspca driver ? regards philippe

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel