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
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
I'm guessing this is related to my problem :) So the question is,
where can I find this module?
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
<!-- AAA ... AAA -->
$ curl -0 -v --data-ascii "$(cat xmldata)" --cert ~/.fedora.cert \
--cacert ~/.fedora-server-ca.cert --key ~/.fedora.cert -k -3 \
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
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>
gpg --keyserver hkp://subkeys.pgp.net --recv-key 38028b72
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
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:
The packages would have no real payload but would have only
a requires list that matches the 3 groups listed in:
- modify mock to act on those packages instead of on group names.
making that act be something you configure so we don't break
the mock update.
- no longer have to worry about groups-file-format-changes screwing up
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