devel

devel@lists.centos.org

1 participants
4619 discussions

ACPI problems on laptops
by carlopmart＠gmail.com 07 Sep '05

07 Sep '05

Hello developers, I have the same problem that this guy has reported on bugzilla under CentOS 4.1: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=154061. My laptop reboots when I do a "shutdown -h now". My kernel version is centos original rpm: kernel-2.6.9-11.EL. Is this problem fixed on a new kernel revision? if not, how can I fix this whitout disabling acpi?? (When acpi is disabled, laptop does a clean shutdown). Thank you very much for your help. P.D: My laptop is an AIRIS Pragma 840. P.D: kernel's dmesg attached. -- CL Martinez carlopmart at gmail dot com

1 0

SPARC build machines perhaps available soon
by Lamar Owen 05 Sep '05

05 Sep '05

PARI has been donated three large Enterprise servers; an E6500, and E6000, and an E5500. I am in process of arranging shipping and pickup, perhaps as soon as next week. Once delivered, I will be setting these beasts up and checking them out, building drive bays, etc. The idea is to install Aurora and bring it up to 1.92, then see abut the buildsystem for CentOS SPARC. The 6500 is destined to replace our Ultra 30 e-mail server, and might even become our webserver as well as a potential buildfarm box for CentOS/SPARC and/or Aurora. Just wanted to keep people updated on this; exciting! -- Lamar Owen Director of Information Technology Pisgah Astronomical Research Institute 1 PARI Drive Rosman, NC 28772 (828)862-5554 www.pari.edu

4 9

Rebuild of glibc fails on CentOS 4.1
by Michael Paesold 22 Aug '05

22 Aug '05

Hi, I hope this is the appropriate list for the given issue. I was in the process of installing Xen on CentOS 4.1, when I ran into the problem that I could not rebuild glibc. (Xen needs a glibc compiled with -mno-tls-direct-seg-refs). The problem is that I cannot rebuild glibc at all (even without any modifications). The build fails during checks (I think it's ntpl) and the build process hangs. There is a defunc ld-linux.so.2 process. If I kill that one, the build goes on and creates rpms, but I guess that glibc must be broken anyway. The check logs give me no clue what could have happened. The problem was already reported in the CentOS forum on 2005/6/21: http://www.centos.org/modules/newbb/viewtopic.php?topic_id=1159 What I did was: * Install minimum CentOS 4.1 from ISOs * update the system using yum * install the toolchain to compile glibc (yum install gd-devel libpng-devel zlib-devel texinfo libselinux-devel gcc gcc-c++ rpm-build + deps) * Created an rpm-root for a regular user ("%_topdir /home/mip/rpm" in .rpmmacros) * as that user: rpm -i glibc-2.3.4-2.9.src.rpm * rpmbuild -ba --target i686 rpm/SPECS/glibc.spec Could you please tell me... * if I am doing something completely wrong? * if you can successfully rebuild glibc with an up-to-date system? * how to find out what really goes wrong here. Thank you very much for any help! Best Regards, Michael Paesold

4 7

automated response
by Robert Galloway 09 Aug '05

09 Aug '05

I will be out of the office until Monday, August 15. If you need immediate assistance, please contact Ben Harper at 801-415-8021. Robert Galloway IKANO Network Operations

1 0

About the translation of the sentence
by Masato Zembutsu 05 Aug '05

05 Aug '05

I didn't have a reply though I did inquiry more than the past Web form. Therefore, it lets me do inquiry even in this ML. I am a linux user in Japan. The information resource of CentOS in on-line system is limited in Japan. It was a matter of last week to know about myself CentOS. I think that Japanese information about CentOS will be spread. So, is it permitted translating information on your Web site into Japanese and introducing it to the public? I want to translate following pages. http : //www.centos.org/modules/smartfaq/ http://www.centos.org/modules/tinycontent/index.php?id=2 http://www.centos.org/modules/tinycontent/index.php?id=3 http://www.centos.org/modules/tinycontent/index.php?id=5 Please tell me if it is necessary about the limitation and the indication before I introduce information to the public. I aim at spreading information on CentOS purely. Though it is introduced to the public on Web, the information which I translated is not a commercial purpose. I keep a fair position by the neutral position to CentOS. Is there a problem in the translation and opening to the public? Would you give me translation and public permission? Or, is permission unnecessary to the translation of the document? I will introduce a sentence to the public without a problem. Regards, // Masato Zembutsu zem(a)pocketstudio.jp ICQ#:5-231-046 // Pocketstudio - http://pocketstudio.jp/ TEL#+81-76-476-9137

1 1

Circular build dependencies in RHCS packages
by Charlie Brady 03 Aug '05

03 Aug '05

"There's a hole in the bucket, Dear Liza, Dear Liza, ..." I'm trying to build all the SRPMS from http://www.linux911.cl/GFS-CENTOS4/, and have found a real dependency mess, including some circular dependencies. Has anyone found a clean way to bootstrap this collection of packages? bash-3.00$ sudo rpm -Uhv /tmp/cman-1.0.1-0.i386.rpm /tmp/ccs- ccs-1.0.1-20050705200822.i386.rpm ccs-devel-1.0.1-20050705200822.i386.rpm bash-3.00$ sudo rpm -Uhv /tmp/cman-1.0.1-0.i386.rpm /tmp/ccs-1.0.1-20050705200822.i386.rpm error: Failed dependencies: magma-plugins is needed by ccs-1.0.1-20050705200822.i386 bash-3.00$ rpmbuild --rebuild magma-plugins-1.0.1-0.src.rpm Installing magma-plugins-1.0.1-0.src.rpm error: Failed build dependencies: gulm-devel is needed by magma-plugins-1.0.1-0.i386 dlm-devel is needed by magma-plugins-1.0.1-0.i386 bash-3.00$ sudo rpm -Uhv /tmp/dlm-devel-1.4.0.8-20050705200822.i386.rpm error: Failed dependencies: dlm = 1.4.0.8-20050705200822 is needed by dlm-devel-1.4.0.8-20050705200822.i386 bash-3.00$ sudo rpm -Uhv /tmp/dlm-devel-1.4.0.8-20050705200822.i386.rpm /tmp/dlm-1.4.0.8-20050705200822.i386.rpm error: Failed dependencies: cman is needed by dlm-1.4.0.8-20050705200822.i386 bash-3.00$ sudo rpm -Uhv /tmp/dlm-devel-1.4.0.8-20050705200822.i386.rpm /tmp/dlm-1.4.0.8-20050705200822.i386.rpm /tmp/cman-1.0.1-0.i386.rpm error: Failed dependencies: ccs is needed by cman-1.0.1-0.i386 bash-3.00$ sudo rpm -Uhv /tmp/dlm-devel-1.4.0.8-20050705200822.i386.rpm /tmp/dlm-1.4.0.8-20050705200822.i386.rpm /tmp/cman-1.0.1-0.i386.rpm /tmp/ccs-1.0.1-20050705200822.i386.rpm error: Failed dependencies: magma-plugins is needed by ccs-1.0.1-20050705200822.i386 bash-3.00$ rpmbuild --rebuild magma-plugins-1.0.1-0.src.rpm Installing magma-plugins-1.0.1-0.src.rpm error: Failed build dependencies: gulm-devel is needed by magma-plugins-1.0.1-0.i386 dlm-devel is needed by magma-plugins-1.0.1-0.i386 bash-3.00$

4 23

CentOS CS & GFS packages
by John Newbigin 02 Aug '05

02 Aug '05

As there seems to be a desire for official CentOS CS & GFS packages, we should decide how these are going to be stored on the mirror. The simple method is probably directories under {3,4} called {CS,GFS}. (ie. new directories alongside extras, centosplus etc). Can these directories easily be shared out to developers? I probably need a new key to sign my packages, unless someone with the 3 key wants to resign them after I sign then with the 2 key. Given the low volume of updates in these trees, it might be easier if someone with 3 access wants to manually take my packages and put them into the 3 tree. Also, how does stuff get into the vault? Is this automatic. -- John Newbigin Computer Systems Officer Faculty of Information and Communication Technologies Swinburne University of Technology Melbourne, Australia http://www.ict.swin.edu.au/staff/jnewbigin

8 19

CentOS on SPARC
by Adam Breaux 31 Jul '05

31 Jul '05

Is this in the works, planned, or never going to happen? -- Adam Breaux breauxaj(a)gmail.com http://www.adambreaux.com

3 4

Yum futex lockup upgrading from 4.0 to 4.1
by Rodrigo Barbosa 18 Jun '05

18 Jun '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Okey, this problem seems to be related to yum. After installing a new 4.0 machine (desktop, so lots of packages, custom install), I pointed CentOS.repos to 4.1. After that, I executed "yum update". Everything started fine, downloads finished without a problem. During the transation, tho, I have a hard locked of the yum process, when finishing updating redhat-lsb. Yum output showed the packted 100% done, but on /proc the process still had the redhat-lsb rpm packged opened (filedescriptor). The python process that was running yum was locked hard on a futex call. Interesting fact to notice that there were no other yum related processes running, and that the running python instance was upgraded earlier during the transation (so I have python.#prelink# running). No signals made any different, and I had to issue a -9 to kill the process (-15 was no good). I had to do a bit of fixing after that, since it seems python doesn't handle broken dependencies very well. Nothing a couple of "rpm -e --justdb" didn't so. Another "yum upgrade" finished upgrading the machine. All my previous tests were from a fully upgraded 4.0 machine, and for those I had no trouble. With this one, a stock 4.0 machine with no upgrades, yum locked. Might be worth trying to reproduce it. Another interesting fact is that this was my only machine with SELinux active, but I'm still betting on a python/yum related problem. All hardware on my machine was fully tested and no problems were detected. No processor overheat, no bad memory, perfect disks. Best regards, - -- Rodrigo Barbosa <rodrigob(a)suespammers.org> "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCs5L9pdyWzQ5b5ckRAuZSAJ9QhSJ29ik7C7z7+elPLoWU/EjLBACfQEMx bIROXJbSmjow3K6fyCPlFmw= =ktV4 -----END PGP SIGNATURE-----

3 2

CentOS 3.5 errors
by John Newbigin 15 Jun '05

15 Jun '05

The following packages from 3.5 do not appear to be signed properly: db4-4.1.25-8.1.i386.rpm db4-devel-4.1.25-8.1.i386.rpm dump-0.4b37-1E.i386.rpm crash-3.10-10.centos.0.i386.rpm db4-java-4.1.25-8.1.i386.rpm I checked on a CentOS-2 and CentOS-3 box. sample problem: $ rpm -vK i386/crash-3.10-10.centos.0.i386.rpm i386/crash-3.10-10.centos.0.i386.rpm: MD5 sum mismatch Expected: 8e030692acbc9af9b7ced6a729410c42 Saw : a27b0ab402bf38be5ae6bf195ca0c355 gpg: Warning: using insecure memory! gpg: please see http://www.gnupg.org/faq.html for more information gpg: Signature made Wed 25 May 2005 20:44:30 EST using DSA key ID 025E513B gpg: BAD signature from "CentOS-3 Key <centos-3key(a)caosity.org>" $ rpm -Kv db4-4.1.25-8.1.i386.rpm db4-4.1.25-8.1.i386.rpm: Header V3 DSA signature: OK, key ID 025e513b Header SHA1 digest: OK (b07a40eedbd1cf5e4703c2164a33af213b6473a3) MD5 digest: BAD Expected(8bcaf8d8b087898cf835d9e6bba73766) != (2023f31e90546d87a3e31714a77f3af3) V3 DSA signature: BAD, key ID 025e513b John. -- John Newbigin Computer Systems Officer Faculty of Information and Communication Technologies Swinburne University of Technology Melbourne, Australia http://www.ict.swin.edu.au/staff/jnewbigin

3 3

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