devel August 2009

devel@lists.centos.org

29 participants
19 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

yum-3.2.8 for Centos 4 backport, part II.
by David Hrbáč 30 Jan '10

30 Jan '10

Hi, I have again worked on yum 3.2.8 for Centos 4 today, after a long time. The result is backported package yum-3.2.8-9.el4.hrb.2.1.5 which is the upgrade of yum-3.2.8-9.el4.hrb.2.1.3 I've been using smoothly for quite a long time. Packages are in testing repos: http://fs12.vsb.cz/hrb33/el4/hrb/testing/i386/repodata/ http://fs12.vsb.cz/hrb33/el4/hrb/testing/x86_64/repodata/ I'd like to ask for QA tests. This patched version passes all the internal yum tests (aka 'make test'). Regards, David Hrbáč

8 43

Documentation Help
by Brad Potts 24 Sep '09

24 Sep '09

Hello, Karanbir Singh told me that I might be able to help CentOS with the 5.3 documentation. He tell me the effort is something Tim Verhoeven has taken under his belt. Can somebody tell me how I might be able to contribute? Some background: I'm a programmer for a living (C#, Java) but am also fairly knowledgeable about awk, sed, perl, a little C, etc. Hope this helps... -- Brad Potts "Comfort is the antidote to success" — Unknown

5 11

yum-3.2.22 in c5-testing
by Karanbir Singh 21 Sep '09

21 Sep '09

Hi, There is a yum-3.2.22 in the c5-testing repo's. This is what will be most likely the next yum update in CentOS-5, so please test. Things that would be good to get feedback on are exactly how the behavior changes for people with modified / customised configs and repo setups. Feedback here on the list would be ideal. http://wiki.centos.org/AdditionalResources/Repositories for info on howto setup the Testing repo if you dont have it already. -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

8 16

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

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel August 2009