devel

devel@lists.centos.org

11 participants
4618 discussions

s390 SIG meeting (May 18, 20:00 UTC)
by Jae-hwa Park 21 May '09

21 May '09

Hello, I found that there were some activities for s390 SIG several months ago, but there were not many people interested in s390 at the time, I think. Karanbir is working on s390x for centos 5.0 now, isn't he? And there might be some people who interested in building s390x port for centos 5.3, so we should talk about this SIG again. The meeting will be held on IRC(#centos-devel) at 20:00 UTC 18th May 2009. (05:00 KST-9 19th May 2009) Anyone interested should join in. Agenda which I thought is like below: 1. where are we? 2. what should we do? - check the build system(real iron) - make build system environment - fix errors - etc. ? - role and responsibility 3. schedule 4. some other topic? If anyone have any other ideas, please post your idea. See you then. Regards, Jerry -- Jae-hwa(Jerry) Park <jaehwa(a)gmail.com>

2 7

RPM date strangeness (was:[CentOS] rpmbuild date shift)
by Ralph Angenendt 20 May '09

20 May '09

David Hrbáč wrote: > Ralph Angenendt napsal(a): > > Yes, I'm seeing that too: > > > > Even if that is changed to UTC, it still is May 13th (and it doesn't explain > > why subsequent changelog entries are one day off, too. > > Thanks Ralph. Yes, it has nothing to do with time zone. It has. I don't know why, yet. > I'm not sure if > I've seen it before last rpmbuild update. Also happens when you use *5.2* in mock to build the packages. And that has an older version of rpm. Watch and cry (I Cc: centos-devel, as I know that JBJ reads there, too). Please do answer in centos-devel, thanks. JBJ: Here's what happens: I take a src.rpm: [angenenr@shutdown SRPMS]$rpm -qp --@hangelog canlock-2b-3.el5.src.rpm |head -2 * Tue May 19 2009 Ralph Angenendt <ralph(a)centos.org> -2b.2 - This is a test bump I rebuild it with rpmbuild: [angenenr@shutdown SRPMS]$rpmbuild --rebuild canlock-2b-3.el5.src.rpm [angenenr@shutdown SRPMS]$rpm -qp --changelog ../RPMS/x86_64/canlock-2b-3.el5.x86_64.rpm |head -2 * Tue May 19 2009 Ralph Angenendt <ralph(a)centos.org> -2b.2 - This is a test bump All is fine. Now let me churn it through mock. [angenenr@shutdown SRPMS]$mock -r centos-5-x86_64 --autocache canlock-2b-3.el5.src.rpm [...] [angenenr@shutdown SRPMS]$rpm -qp --changelog /var/lib/mock/centos-5-x86_64/result/canlock-2b-3.el5.x86_64.rpm |head -2 * Wed May 20 2009 Ralph Angenendt <ralph(a)centos.org> -2b.2 - This is a test bump Ummm? [angenenr@shutdown SRPMS]$date Tue May 19 13:19:25 CEST 2009 Yay! I invented a time machine! (or someone did). Okay, let's move the machine from Germany to the UK [angenenr@shutdown SRPMS]$sudo cp /usr/share/zoneinfo/Europe/London /etc/localtime [angenenr@shutdown SRPMS]$date Tue May 19 12:20:17 BST 2009 [angenenr@shutdown SRPMS]$rpm -qp --changelog /var/lib/mock/centos-5-x86_64/result/canlock-2b-3.el5.x86_64.rpm |head -2 * Tue May 19 2009 Ralph Angenendt <ralph(a)centos.org> -2b.2 - This is a test bump Hmmm. Who moved the international date line to the Channel? What about mock? Let's move the machine back to Germany first. [angenenr@shutdown SRPMS]$sudo cp /usr/share/zoneinfo/Europe/Berlin /etc/localtime [angenenr@shutdown SRPMS]$date Tue May 19 13:22:08 CEST 2009 [angenenr@shutdown SRPMS]$mock -r centos-5-x86_64 shell init mock-chroot> date Tue May 19 07:22:18 EDT 2009 So mock uses EDT which is 6 hours behind. Which does not explain why moving from BST (EDT +0500) still gives me the correct date in the changelog, moving the machine one step further to CEST (EDT +0600) moves me to the next day, though. What about the rpm built with rpmbuild? Let's move the machine to Sidney: [root@shutdown etc]# cp /usr/share/zoneinfo/Australia/Sydney localtime [root@shutdown etc]# date Tue May 19 21:27:50 EST 2009 [root@shutdown etc]# rpm -qp --changelog /home/angenenr/redhat/RPMS/x86_64/canlock-2b-3.el5.x86_64.rpm * Tue May 19 2009 Ralph Angenendt <ralph(a)centos.org> -2b.2 - This is a test bump Strange. This is 8 hours in the future (and not 6), but still shows me the correct date. Something is not right here. Is this something to worry about? How and why does that happen? Why are there even calculations on the date line in a changelog? Cheers, Ralph

3 8

kmod update with yum
by Farkas Levente 19 May '09

19 May '09

hi, i need some help:-( i now spend many hours to find the reason why yum always install kmod rpms on centos and never update. currently there is not any weak-updates kmod rpm in centos which has more version-release, but as you try to update any kmod the same problem will arise. in case of fedora where kmod's are hardwired to a given kernel it's not a problem (but those are never weak-update kmods), but in case of centos where eg in 5.3 all kernel a kabi compatible then we can use none kernel version specific kmods. what's more in case of weak-updates kmod when the same package has more version installed cause many problems. suppose i've got a kmod installed eg: # rpm -q kmod-fuse kmod-fuse-2.7.4-20.el5 now i build a new one and try to update with yum update. it's always install it and i can't force yum to update it. anybody can tell me the reason? of course rpm -U update it. imho it's the same reason as the recent dbrd kmod thread where wasn't any solution. anyway anybody know what is the yum-kmod and what is it good for? and try both with/without yum-kmod but the same happened:-( -- Levente "Si vis pacem para bellum!"

1 1

Re: [CentOS-devel] [PHP 5.2.6] Feedback / Centos Testing andCentOS Extras
by Paulo Martinez 17 May '09

17 May '09

Am 06.05.2009 um 12:04 schrieb Karanbir Singh: > Anthony Francis wrote: >> I just installed this release without issue. I want to thank the >> maintainers for getting 5.2 on there. My application depends on >> the new >> built in JSON parser. > > Thanks for the feedback! JFI: There is a php 5.1.6 dependence. If php 5.2.6 of c5-testing is installed squirrelmail-1.4.8-5.el5.centos.3 complains about it Warning: preg_split() expects parameter 4 to be long, string given in /usr/share/squirrelmail/functions/imap_messages.php on line 808 Warning: Invalid argument supplied for foreach() in /usr/share/squirrelmail/functions/mime.php on line 52 Looking forward ... Regards P.M.

1 0

debuginfo out of date
by Phil Schaffner 15 May '09

15 May '09

Another one from the Fora: http://www.centos.org/modules/newbb/viewtopic.php?viewmode=flat&topic_id=20… Thread started by robertsong: centos 5.3 glibc debuginfo is not updated "Hello, I have updated to centos 5.3, the latest version of glibc-2.5-34. but I found the debuginfo rpm package was not updated to this version. Now the debuginfo version is 2.5.24 in http://debuginfo.centos.org/5/i386/. glibc-debuginfo-2.5-24.i686.rpm glibc-debuginfo-common-2.5-24.i386.rpm When would the rpm be updated ?" In investigating this I noticed that the Forum user is correct and that the metadata in the arch-specific directories is even older than the packages. Those ought to be either re-generated or removed. From http://debuginfo.centos.org/5/x86_64/repodata/ [ ] filelists.xml.gz 23-Oct-2007 20:41 3.0M [ ] other.xml.gz 23-Oct-2007 20:41 4.0M [ ] primary.xml.gz 23-Oct-2007 20:41 255K [TXT] repomd.xml 23-Oct-2007 20:41 951 I reviewed recent debuginfo threads and could not find anything on this issue. I presume the repo config should be something like: #Debug Info [debuginfo] name=CentOS-$releasever - DebugInfo #baseurl=http://debuginfo.centos.org/$releasever/$basearch/ baseurl=http://debuginfo.centos.org/$releasever/ gpgcheck=1 enabled=0 gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-$releasever protect=1 priority=1 Is there a mirrorlist mechanism for debuginfo? Phil

3 6

CDS or CentOS Directory Server - Final testing
by Tim Verhoeven 14 May '09

14 May '09

Hi, The what should be final packages of CDS are available in the testing repo (http://dev.centos.org/centos/5/testing/) If people could give these a final test to see if they are ok ? They are up to date to what is currently available for RHDS (version 8.1). If nothing is found these will move to the producion repos (probably Extras) in a couple of days. Thanks for testing, 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)

2 3

Re: [CentOS-devel] An introduction and a s390 effort
by Jae-hwa Park 14 May '09

14 May '09

Hi, I'm also interested in s390 build for CentOS. I have a real iron, z9 system for test. So I think it might be helpful for building. Nice to meet you. :-) ah, I'm a zLinux engineer since 2000, and now I'm working as a engineer for technical support of zLinux in Korea. Please let me know what should I do first. -- Jae-hwa(Jerry) Park <jaehwa(a)gmail.com> 2009/3/19 Karanbir Singh <mail-lists at karan.org>: > Sascha Thomas Spreitzer wrote: >> My name is Sascha Thomas Spreitzer and I live in the eastern outback >> of Munich in Bavaria Germany. > > Thanks for dropping in and showing interest. There is a s390 build > initiative in progress at this time, and I am sure we can use a few more > eyes on that side of things. Over the next few days, I'll try and > establish a more focused group. > > -- > Karanbir Singh {kbsingh at karan.org} > http://www.karan.org/ ICQ: 2522219 Yahoo IM: z00dax > GnuPG Key : http://www.karan.org/publickey.asc > _______________________________________________ > CentOS-devel mailing list > CentOS-devel at centos.org > http://lists.centos.org/mailman/listinfo/centos-devel

4 12

Re: [CentOS-devel] RPM Contribution
by David Dreggors 13 May '09

13 May '09

Ralph, I see now what you are saying. I went to the Dasha project page. I tried my wiki login and it failed so should I sign up for an account there as well? This is all getting quite monotonous... I now have a login for the CentOS forums, one for the wiki, one for each mail list (devel and docs), and now I am to register again for the Dasha project? Is there no way to unify this to a single login across the whole site? While the logins are the same for the forums and the lists, the wiki had to be different (wiki wants camel case). Not to mention if I am working one the wiki or the forum I have to login seperately. Then add to that if I want to login now to the dasha... do I have to login yet again? I am sorry I do not wish to complain really... I just wish to offer that this seems like a large amount of work to ask a contributor. If it cannot be helped for now, that is just the way it is. I just though it might be worth asking about.

3 10

(no subject)
by Jenny Pérez 12 May '09

12 May '09

1 0

RPM contribution
by David Dreggors 11 May '09

11 May '09

Sorry for the double post if there is one. I never saw the first hit the list and I relized I had sent from the wrong account. I would like to contribute an rpm that I built. The rpm is the latest snapshot of the madwifi driver which includes support for the Atheros AR5007EG. This is a popular card and is not supported currently under the ath5k module or the older madwifi driver. I have attached the spec file and the link to the src.rpm is: http://ddhj.homeip.net/madwifi/madwifi-hal-0.10.5.6-6.src.rpm # #Gen the last kernel-devel available on the machine. %{!?kernel: %{expand: %%define kernel %(rpm -q kernel-devel --last | head -1 | awk '{print $1}' | sed s/kernel-devel-// )}} %if %(echo %{kernel} | grep -c smp) %{expand:%%define myksmp -smp} %endif #Define the latest kernel installed %define mykversion %(echo %{kernel} | sed -e s/smp// -) %define mykrelver %(echo %{mykversion} | tr -s '-' '_') #rpm -q kernel --last | head -1 | awk '{print $1}' | sed s/kernel-// | sed -e s/smp// - | tr -s '-' '_' # Define based on the tar ball extract. # Those two variable will be instanced during the tarball generation %define revision r4016 %define snapshot 20090429 # branch is not used yet. %define branch hal-0.10.5.6 Summary: A linux device driver for Atheros chipsets (ar5210, ar5211, ar5212). Name: madwifi-hal Version: 0.10.5.6 Release: 6 License: GPL2 Group: System Environment/Kernel URL: http://madwifi.org Source0: http://snapshots.madwifi-project.org/madwifi-hal-0.10.5.6/madwifi-hal-0.10.… BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-%{revision}-%{snapshot} Requires: /sbin/depmod Requires: %{name}-module >= %{version} BuildRequires: /sbin/depmod BuildRequires: /lib/modules/%{mykversion}/build/Makefile %description This software contains a Linux kernel driver for Atheros-based Wireless LAN devices. The driver supports station, AP, ad-hoc, and monitor modes of operation. The Atheros driver depends on a device-independent implementation of the 802.11 protocols that originated in the BSD community (NetBSD in particular). The driver functions as a normal network device and uses the Wireless Extensions API. As such normal Linux tools can and should be used with it. Where the wireless extensions are lacking private ioctls have been added. There is only one driver included here; it supports PCI, miniPCI and Cardbus devices - USB devices are currently not supported by this driver! The driver can be built as a module or linked directly into the kernel. Note however that the net80211 layer is device-independent; there is no reason it cannot be used with any 802.11 device (in fact on BSD systems this is the case). There are currently 4 "programming generations" of Atheros 802.11 wireless devices (some of these have multiple hardware implementations but otherwise appear identical to users): 5210 supports 11a only 5211 supports both 11a and 11b 5212 supports 11a, 11b, and 11g 242x supports 11a, 11b, and 11g %package module Summary: A linux device driver for Atheros chipsets (ar5210, ar5211, ar5212, ar242x). Group: System Environment/Kernel Requires: kernel = %{mykversion} Release: 6_%{mykrelver} %description module This software is broken into multiple modules. The Atheros-specific device support is found in the ath_pci module; it should be loaded when an Atheros wireless device is recognized. The ath_pci module requires an additional device specific module, ath_hal, which is described more below. In addition the driver requires the wlan module which contains the 802.11 state machine, protocol support, and other device-independent support needed by any 802.11 device. This code is derived from work that first appeared in NetBSD and then FreeBSD. The wlan module may also force the loading of additional modules for crypto support (wlan_wep, wlan_tkip, wlan_ccmp, etc.), for MAC-based ACL support (wlan_acl), and for 802.1x authenticator support (wlan_xauth). The latter modules are only used when operating as an AP. The crypto modules are loaded when keys of that type are created. %prep %setup -q -n %{name}-%{version}-%{revision}-%{snapshot} find . -name Makefile\* | xargs perl -pi -e's,/sbin/depmod,: /sbin/depmod,' %build export MANDIR=/usr/share/man export KERNELRELEASE=%{mykversion} export KERNELPATH=/lib/modules/%{mykversion}/build export KERNELCONF=/lib/modules/%{mykversion}/build/.config export KMODPATH=/lib/modules/%{mykversion}/net export COPTS="-I /lib/modules/%{mykversion}/build/include/ $COPTS" make %install export MANDIR=/usr/share/man export KERNELRELEASE=%{mykversion} export KERNELPATH=/lib/modules/%{mykversion}/build export KERNELCONF=/lib/modules/%{mykversion}/build/.config export KMODPATH=/lib/modules/%{mykversion}/net rm -rf %{buildroot} # make info mkdir -p %{buildroot}/usr/local/bin mkdir -p %{buildroot}/$KMODPATH mkdir -p %{buildroot}/usr/share/madwifi make install DESTDIR=%{buildroot} KERNELPATH=/lib/modules/%{mykversion}/build MANDIR=/usr/share/man # cd tools ; make install DESTDIR=%{buildroot} KERNELPATH=/lib/modules/%{mykversion}/build BINDIR=/usr/local/bin ; cd .. %post module if [ $1 == 1 ] then echo "#Madwifi Driver" >> /etc/modprobe.conf echo "alias ath0 ath_pci" >> /etc/modprobe.conf echo "#Madwifi Driver" >> /etc/modprobe.d/blacklist echo "blacklist ath5k" >> /etc/modprobe.d/blacklist fi /sbin/depmod -ae %{mykversion} %postun module if [ $1 = 0 ] then /bin/sed -i 's/#Madwifi Driver//' /etc/modprobe.conf /bin/sed -i 's/alias ath0 ath_pci//' /etc/modprobe.conf /bin/sed -i 's/#Madwifi Driver//' /etc/modprobe.d/blacklist /bin/sed -i 's/blacklist ath5k//' /etc/modprobe.d/blacklist fi /sbin/depmod -ae %{mykversion} %clean rm -rf %{buildroot} %files %doc COPYRIGHT README INSTALL THANKS %attr(0755,root,root) /usr/local/bin/* %attr(0644,root,root) /usr/share/man/man8/* %files module %defattr(-,root,root,-) /lib/modules/%{mykversion}/net/*.*o %attr(0644,root,root) /usr/share/man/man8/* # %changelog * Sun May 10 2009 David Dreggors <ddreggors(a)cfl.rr.com> - Create RPM of snapshot: 20090429 of release: r4016 * Wed Dec 14 2005 Patrick Pichon <Patrick.Pichon(a)laposte.net> - Update accordingly to the new file name rule: madwifi-ng-r<revision>-<generation date>.tar.gz - 'branch' tag is not use yet. 'ng' is hardcoded as part of the file name - Change the computation to target the latest kernel-devel env. * Thu Nov 3 2005 Patrick Pichon <Patrick.Pichon(a)laposte.net> - Incorporate the changes made on the Makefile - Cleaning on the Description fields - Changing the URL to the new madwifi.org's one. - Install under /usr/share/doc/madwifi-release the INSTALL and THANKS files - Install under /usr/share/doc/madwifi-release the docs files. * Sun Oct 30 2005 Patrick Pichon <Patrick.Pichon(a)laposte.net> - Add Man pages * Mon Oct 24 2005 Lyonel Vincent <> - Fix the --rebuild option. * Mon Oct 3 2005 Lyonel Vincent <> - Build by default on latest kernel installed * Wed Jul 20 2005 Patrick Pichon <Patrick.Pichon(a)laposte.net - target particular kernel * Mon Oct 27 2004 Patrick Pichon <Patrick.Pichon(a)laposte.net> - Handle 2.4 kernel * Mon Sep 21 2004 Lyonel Vincent <> - change the naming of the kernel module part. * Mon Aug 23 2004 Patrick Pichon <Patrick.Pichon(a)laposte.net> - Update WPA has been merged into HEAD * Mon Jul 27 2004 Patrick Pichon <Patrick.Pichon(a)laposte.net> - Update to handle WPA branch. * Tue Jul 08 2004 Patrick Pichon <Patrick.Pichon(a)laposte.net> - Initial Release

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