buildsys January 2006

buildsys@lists.fedoraproject.org

6 participants
5 discussions

Start a nNew thread

Extras build system back up
by Dan Williams 26 Oct '06

26 Oct '06

Hi, We're back up and using the latest plague code. yum update your plague-client and you should be good to go. Dan

3 7

pthread_sigmask module
by Jeff Sheltren 01 Feb '06

01 Feb '06

Hi, I am having some problems with the build server hanging (ie. there are no jobs running, but when I submit a job it sits with status 'waiting')... Since this is running on EL4 (python 2.3.4), I'm getting this message when I start up plague-builder: WARNING: You might want to install the pthread_sigmask module. Python versions earlier than 2.4 have problems with signals and spawned processes. I'm guessing this is related to my problem :) So the question is, where can I find this module? Thanks, Jeff

2 2

SSL connection errors to plague-server
by Enrico Scholz 24 Jan '06

24 Jan '06

Hello, somehow, SSL connections to plague-server are broken currently. When the sent request is <1024 bytes it seems to hang forever. Reproducible e.g. by: ---------- $ cat >xmldata <<EOF <?xml version="1.0"?> <methodCall> <methodName>examples.getStateName</methodName> <params> <param> <value><i4>41</i4></value>  </param> </params> </methodCall> EOF $ curl -0 -v --data-ascii "$(cat xmldata)" --cert ~/.fedora.cert \ --cacert ~/.fedora-server-ca.cert --key ~/.fedora.cert -k -3 \ https://buildsys.fedoraproject.org:8887/RPC2 ---------- When the '' placeholder is kept as-is (--> <1024 Bytes), curl won't return. Filling it with some chars make curl return correctly. Related code for a curl-based plague-client worked a week ago but hangs now. Enrico

2 4

[RFC] plague and mock and other log files
by Ignacio Vazquez-Abrams 09 Jan '06

09 Jan '06

What might be useful is to create a directory in the mock buildroot (e.g., /logs) and be able to have the spec file dump files in there, at which point when mock is finished plague would take the contents of that directory and add them to the three log files normally found after a build. That way files like config.log would no longer be such a pain to deal with if a build fails. -- Ignacio Vazquez-Abrams <ivazquez(a)ivazquez.net> http://fedora.ivazquez.net/ gpg --keyserver hkp://subkeys.pgp.net --recv-key 38028b72

2 1

mock and fc5/fe5 and comps pain
by seth vidal 05 Jan '06

05 Jan '06

Hi, As some of you are aware the comps changes that anaconda wanted changed how comps works in yum which nicely BROKE Fedora Extras rawhide builds once the comps.xml changes landed in rawhide. So what do we do to fix it? Jeremy and I tossed around a couple of ideas - none of them terribly attractive but we settled on this, I'd like to hear some input: - make three packages and put them in the buildgroups repo: http://fedoraproject.org/buildgroups/ The packages would have no real payload but would have only a requires list that matches the 3 groups listed in: http://fedoraproject.org/buildgroups/4/i386/buildroots.xml - modify mock to act on those packages instead of on group names. Possibly making that act be something you configure so we don't break everyone with the mock update. - no longer have to worry about groups-file-format-changes screwing up mock and extras builds So what do y'all think? That sound like a plan? Would someone like to make the packages for us while I go futz with mock? thanks, -sv

8 21

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

buildsys January 2006