May 2011 - devel - lists.centos.org

anaconda dependency calculation?
by Nicholas Byrne 04 Aug '25

04 Aug '25

Hi all, I'm trying to find a tool that calculates all dependencies for a specific package or group of packages for use with CentOS 5 (beta) with the intention of putting together a custom single CD build of CentOS 5. With CentOS 4 i used a python script that used the hdrlist module to find all dependencies which borrowed code from a number of sources. I've looked at yumdownloader and how it checks dependencies (using the --resolve option) but if i pass it the list of packages defined in say the Base and the Core yum groups which generally form an absolute minimal install i end up with about 200 packages. If i do a custom install (using beta 1 disks) and deselect everything i end up with over 300 packages. So i'm guessing anaconda calculates dependencies in a slightly different way, can anyone point me to files/code where i should be looking to find out? Thanks very much in advance for help Nick This e-mail is the property of Quadriga Worldwide Ltd, intended for the addressee only and confidential. Any dissemination, copying or distribution of this message or any attachments is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from Quadriga may be monitored. Quadriga cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of Quadriga.

6 11

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

Interested in IA64 build.
by James A. Peltier 22 Jan '13

22 Jan '13

I noticed on the SIG that people interested in other ports of interest. I'd like to express interest in the IA64 port. What is the best way to get started? I have two SGI Itanium 2 based machines. One 64 processor x 64GB SGI Altix and a 32 processor x 32GB RAM SGI Prism. They are currently running CentOS 4.8 and I would love to be able to run CentOS 5.5 on them to get them into compliance with the rest of the cluster. -- James A. Peltier Systems Analyst (FASNet), VIVARIUM Technical Director Simon Fraser University - Burnaby Campus Phone : 778-782-6573 Fax : 778-782-3045 E-Mail : jpeltier(a)sfu.ca Website : http://www.fas.sfu.ca | http://vivarium.cs.sfu.ca MSN : subatomic_spam(a)hotmail.com Does your OS has a man 8 lart? http://www.xinu.nl/unix/humour/asr-manpages/lart.html

9 53

CentOS-[56] Continous Release
by Karanbir Singh 22 Jun '11

22 Jun '11

hi, Johnny and I spoke about this a few days back and we think the best way to solve the problem around delayed srpms + waiting for isos, build and QA at the time of a point release is to get something like a 'Continous Release' repository going. The Problem: At a point release stage, users dont get updates till such time as the ISOS are ready ( eg. during the 5.6 release process ), the updates are built, QA has had time to verify content and the mirrors sync up. For new installs, this isnt an issue; however for people with existing installs this can potentially expose their installations. One solution: Export packages as they are built from the c[456]bsys into a repository that people can opt into, that would allow them to get early access to packages. Couple of notes: - it would have to be opt-in, rather than default for everyone - packages into the CR repo's will not be announced via the regular channels; the announcements will still only happen when rpms are visible in the os/ and updates/ repos. - it will not mean a lesser or a worse quality of builds, we hope to have enough automation in place that rpms will only be released into this repo once we are sure that it meets the release requirements. - this repository will run off centos.org machines initially, and will not be released to third party mirrors. The exact details of how the release-to-external-mirrors takes place, and how we manage the issues around that would be a conversation we can relegate into the future for now. - the CR repos will go-away once rpms are released in the regular process, it will not transfer into a rolling release type repo. At this stage, we are looking for comments as we prep for future release process. - KB

13 71

CentOS 6 status update (relayed from the web forum)
by Matthew Miller 05 Jun '11

05 Jun '11

<https://www.centos.org/modules/newbb/viewtopic.php?topic_id=25878&forum=53> My current understanding is that the ongoing build of CentOS 6.0 is still running in minimal mode. I expect it to pick up speed once all the current CentOS 5.6 updates have been built and pushed to the update queue. I will be discussing the 6.0 build status with Karanbir in the next few days and hopefully will have something a little less tenuous to report early-ish next week. I think it is fair to say that as CentOS 6.0 is a new entry into the product line, it may spend somewhat more time in QA whilst the critical eyes give it close scrutiny. -- Alan Presumably, this means that it is reasonable to expect a longer window than the early optimistic estimates of two weeks after the CentOS 5.6 release. -- Matthew Miller mattdm(a)mattdm.org <http://mattdm.org/>

19 35

Using https repository through proxy
by Julien.GILLES＠sungard.com 26 May '11

26 May '11

Hi, for various reasons I am trying to install a private repository for Centos 5, and I would like to use HTTPS only connections. The servers must access to this repository through a proxy. In the .repo file I have configured : baseurl=https://my.repository/pkg/stable/$basearch The proxy is defined correctly. yum fails with: https://my.repository/pkg/stable/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 501: Not Implemented Trying other mirror. Error: Cannot retrieve repository metadata (repomd.xml) for repository: Please verify its path and try again. Using a fake proxy shows me that the request sent by yum is not correct (ie GET https://... Instead of a classical CONNECT request). I have found (thanks google) that this bug is known, seems related to urllib2.py and httplib.py from python 2.4, but I can't find a way to make it works. The patches and the solution are quite old, and does not seems to apply (or I am doing something wrong). Futhermore the bug is known from Redhat https://bugzilla.redhat.com/show_bug.cgi?id=208852 since a long time, and according bugzilla has been corrected in 2006 ! Well, I don't know where to look at now, so help appreciated ! -- Julien Gilles.

4 7

Help with LiveCD for 6.0
by Jeff Sheltren 25 May '11

25 May '11

If someone is willing to help, we need assistance in creating the LiveCD for CentOS 6.0. There is a task in the QAWeb tracker for this here: http://qaweb.dev.centos.org/qa/node/65 If you are willing/able to help, please reply here or we can discuss in #centos-devel or #centos-social - I'm Jeff_S there. Thanks, Jeff

13 27

debuginfo.centos.org offline
by Phil Schaffner 18 May '11

18 May '11

The debuginfo site has been unavailable at least since yesterday: https://www.centos.org/modules/newbb/viewtopic.php?post_id=133867&topic_id=…

2 1

QA Testing - QAWeb Community Site
by Jeff Sheltren 12 May '11

12 May '11

We now have a site up which will be the central location for the QA efforts on CentOS: http://qaweb.dev.centos.org/qa We're starting to use this for the 6.0 release, though I would consider it to still be in a "testing" phase. We need to figure out what works well here and what doesn't so that we can improve it for future releases. You'll notice as you go to the site that there is a calendar with target dates for the 6.0 release. I'm not guaranteeing that we'll make those, but that's what we're aiming for. Also, you'll see a case tracker which is where we'll track bugs and TODOs. There's one there currently which could use some attention which is the LiveCD creation. If you're interested in helping that effort, please read over the ticket and the linked sites for more info and chime in on the ticket to help (not this email thread please). Aside from that, there's not much there at the moment. I'm envisioning that the QA team will use the Notebook section for reporting on tests done, and the case tracker for reporting bugs/issues that arise during testing. This is still a work in progress, so it may be changing as we go along. For starters, we will be working on adding an RSS feed to the QA group so that people can easily track activity there without having to visit the website frequently. Thanks to everyone who was involved in getting the site up! -Jeff

11 14

centos 5.5 -> 5.6 pushout
by Florian La Roche 12 May '11

12 May '11

Hello, running "/usr/sbin/hardlink" on the CentOS 5.5 and 5.6 directory saves 2 GB of disk space. Not huge, but if that is done on the main server once, all rsync mirrors would pick this up. Reducing the overall mirror space needed and the size of new data for a CentOS Update release should be important. best regards, Florian La Roche

2 1

Public QA Testing?
by Mike Doroshenko 11 May '11

11 May '11

The calendar on the QA site says ISOs will be pushed to QA this Saturday. Will these ISOs be made public for testing or do I need to join the QA Team? I have some machines that I can run test installs on.

4 3

WebSite V2 - progress
by Marian Marinov 11 May '11

11 May '11

Hello guys, we have done some progress on the new web site project. We need your comments for the design of the front page. We have 3 proposals or the design of the frontpage. Please look at them, we need your help :) http://qaweb.dev.centos.org/websitever2/ Best regards, Marian

12 22

Missing updates? gdb, openoffice.org, openldap
by Andreas Rogge 09 May '11

09 May '11

Upstream has released three Errata which have not (yet?) made it into CentOS http://rhn.redhat.com/errata/RHBA-2011-0178.html (openldap Bugfix) http://rhn.redhat.com/errata/RHSA-2011-0182.html (openoffice.org Important) http://rhn.redhat.com/errata/RHBA-2011-0186.html (gdb Bugfix) Are these missed, skipped or maybe in build or qa? Sorry if that was already brought up on the list earlier. Regards, Andreas -- Solvention Ltd. & Co. KG Egermannstr. 6-8 53359 Rheinbach Tel: +49 2226 158179-0 Fax: +49 2226 158179-9 http://www.solvention.de mailto:info@solvention.de

7 13

Missing announcements CESA-2011:0312 / CESA-2011:0374
by Andreas Rogge 09 May '11

09 May '11

CESA-2011:0374 5.6/updates/x86_64: thunderbird-2.0.0.24-15.el5.centos.x86_64.rpm 5.6/updates/i386: thunderbird-2.0.0.24-15.el5.centos.i386.rpm The packages belong to CESA-2011:0374 which was never announced. CESA-2011:0312 5.6/updates/x86_64: thunderbird-2.0.0.24-14.el5.centos.x86_64.rpm 5.6/updates/i386: thunderbird-2.0.0.24-14.el5.centos.i386.rpm The packages belong to CESA-2011:0312 which was never announced. -- Solvention Ltd. & Co. KG Egermannstr. 6-8 53359 Rheinbach Tel: +49 2226 158179-0 Fax: +49 2226 158179-9 http://www.solvention.de mailto:info@solvention.de

2 1

Missing announcement CESA-2011:0310
by Andreas Rogge 09 May '11

09 May '11

The following packages are in 5.6/updates/x86_64: firefox-3.6.14-4.el5.centos.i386.rpm firefox-3.6.14-4.el5.centos.x86_64.rpm xulrunner-1.9.2.14-4.el5.i386.rpm xulrunner-1.9.2.14-4.el5.x86_64.rpm xulrunner-devel-1.9.2.14-4.el5.x86_64.rpm xulrunner-devel-1.9.2.14-4.el5.i386.rpm The following packages are in 5.6/updates/i386: firefox-3.6.14-4.el5.centos.i386.rpm xulrunner-1.9.2.14-4.el5.i386.rpm xulrunner-devel-1.9.2.14-4.el5.i386.rpm The packages belong to CESA-2011:0310 which was never announced. -- Solvention Ltd. & Co. KG Egermannstr. 6-8 53359 Rheinbach Tel: +49 2226 158179-0 Fax: +49 2226 158179-9 http://www.solvention.de mailto:info@solvention.de

2 1

Missing announcement CEBA-2010:0227
by Andreas Rogge 09 May '11

09 May '11

CentOS 5 x86_64 updates contains: etherboot-pxes-5.4.4-13.el5.centos.x86_64.rpm etherboot-roms-5.4.4-13.el5.centos.x86_64.rpm etherboot-roms-kvm-5.4.4-13.el5.centos.x86_64.rpm etherboot-zroms-5.4.4-13.el5.centos.x86_64.rpm etherboot-zroms-kvm-5.4.4-13.el5.centos.x86_64.rpm This belongs to CEBA-2010:0227 and is x86_64 only. Neither CEBA-2010:0227 nor any of the above packages been announced. There's also some more weird stuff we're hitting. I will bring it up on the list unless someone tells me to stop. Regards, Andreas -- Solvention Ltd. & Co. KG Egermannstr. 6-8 53359 Rheinbach Tel: +49 2226 158179-0 Fax: +49 2226 158179-9 http://www.solvention.de mailto:info@solvention.de

1 0

Missing Package spice-usb-redirector / CEEA-2010:0460
by Andreas Rogge 09 May '11

09 May '11

I just noticed that the following packages which were announced as CEEA-2010:0460 [1],[2] but never made it onto the mirrors: spice-usb-redirector-4.5-2.el5_5.i386.rpm spice-usb-redirector-4.5-2.el5_5.x86_64.rpm Regards, Andreas [1] http://lists.centos.org/pipermail/centos-announce/2010-June/016719.html [2] http://lists.centos.org/pipermail/centos-announce/2010-June/016721.html -- Solvention Ltd. & Co. KG Egermannstr. 6-8 53359 Rheinbach Tel: +49 2226 158179-0 Fax: +49 2226 158179-9 http://www.solvention.de mailto:info@solvention.de

4 7

Confusing package versioning
by Ned Slider 06 May '11

06 May '11

Hi Johnny et al., I'd like to raise a query relating to recent package versioning. For example, CentOS recently released the following updates: httpd-2.2.3-45.el5.centos.1.src.rpm selinux-policy-2.4.6-300.el5_6.1.src.rpm relating to the upstream packages: httpd-2.2.3-45.el5_6.1.src.rpm selinux-policy-2.4.6-300.el5_6.1.src.rpm which IMHO is confusing. In the case of selinux-policy (and others) CentOS rigorously follows the upstream versioning, yet for httpd the versioning is different. Firstly, IMHO it is difficult to establish that the two (httpd) packages are indeed the same, and secondly, one wonders how CentOS might handle the notional upstream release of httpd-2.2.3-45.el5_7.1.src.rpm, for example. Where it is necessary to append the centos tag, I would assume it would be preferable to do it at the end of the existing release string thus preserving the upstream notation. For example, httpd-2.2.3-45.el5_6.1.centos.src.rpm I realise it's not easy when upstream do things like this: Release: 45%{?dist}.1 but at the very least it would be nice if you could set %{dist} to el5_6.centos in this case which would be a closer match to upstream As it stands, it looks like the centos.1 was appended by CentOS and the original upstream package was httpd-2.2.3-45.el5.src.rpm which clearly isn't the case. In such cases, would editing the SPEC file release line be the lesser of two evils?

12 60

redhat-logos bug?
by Farkas Levente 05 May '11

05 May '11

hi, in redhat-logos-4.9.99-11.el5.centos.src.rpm there are source Source8: gnome-splash.png Source9: redhat-credits.png but source 9 never used while source 8 used twice: cp -f %{SOURCE8} gnome-splash/ cp -f %{SOURCE8} pixmaps/ is it a bug or feature? -- Levente "Si vis pacem para bellum!"

3 5

sata_via and WD drives incompatibility patch
by Dmitry E. Mikhailov 04 May '11

04 May '11

Greetings, I was hit by an infamous hardware incompatibility between VIA VT6420/1 sata card (sata_via) and newer Western Digital drives. The bug has been worked around in mainline kernel at 2.6.32.7, * https://bugzilla.kernel.org/show_bug.cgi?id=15173 * http://article.gmane.org/gmane.linux.ide/46352 * http://thread.gmane.org/gmane.linux.kernel/1062139 The sata_via patch from bug#15173 applies cleanly to sata_via module of 2.6.18-238 and now I'm running using a 'fixed' module with no problem. Unfortunately the patched module uses symbols not from kABI whitelist so universal replacement kernel module could not be made, but the patch itself could be integrated to upstream's tree or into the CentOS-Plus kernel. As I'm not a RHEL subscriber, I can only ask for the latter. Any ideas? Best regards, Dmitry Mikhailov

3 2

updateinfo.xml
by Baptiste AGASSE 04 May '11

04 May '11

Hi all, It could be useful to make "yum updates --security" work, and now, spacewalk (since 1.4) can generate erratas from this file. Thanks for yours answers. Regards.

2 3

Test scripts - some starter questions.
by Steve Barnes 04 May '11

04 May '11

Hi list A few questions regarding the scope of test scripts that have been requested: - is there a git repository or similar source that contains all of the currently available test scripts? It would be helpful to know that, given my copious spare time, I'm not re-inventing any wheels or contributing the 57th LAMP install script. - relating to package installation test scripts, would there be any appreciable benefit to simply throwing everything + kitchen sink at the wall and see what _doesn't_ stick? (i.e., yum install every single available package one after the other and record any failures?) This seems like a more...comprehensive method of uncovering package installation issues than me simply picking "my top 10 favourite/most well known" yum packages. - is the scope for test scripts "anything you can think of that performs some kind of configuration change with a measurable return value" - e.g, tests that cover (for example) networking configuration, partition/filesystem creation, package installation, firewall configuration, user/group account creation/deletion/editing, SSH key generation etc etc etc? - at present, each test script needs to be self-contained. To reduce the amount of code duplication/maintenance is there any intention (or objection) to developing a library of helper functions? Thank you! Steve

4 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel May 2011