Extras build system back up
by Dan Williams
Hi,
We're back up and using the latest plague code. yum update your
plague-client and you should be good to go.
Dan
16 years, 11 months
Best way to sign packages before adding to the repos?
by Chris Weyl
Hey all--
Ok, so here's a question. What's the best way to sign a package(s)
before adding it to the repository? I was thinking that the easiest
way to do this would be while it's sitting in the "needsign/success"
state, but it looks like it's actually being added to the repository
before that state.
Is there an easy way to do this? Or even a not-so-easy one? <grin>
-Chris
17 years, 9 months
Patch to store user info in different DB engines
by Jeff Sheltren
I'm attaching a patch which uses DBManager for interacting with the
user database rather than always relying upon sqlite. This way, if
you use pgsql or mysql for your database back-end, user information
will be stored there as well.
The problem is, this will screw up current installations which are
using pgsql/mysql because the old code assumes sqlite is used for
user info, so suddenly your user database will be empty... I guess
the easiest way around this is to write a quick script to pull
everything out of the sqlite database and put it into mysql/pgsql.
Also, I'll look at updating the user-manager.py script. In fact, I
guess it may be easiest to add export/import functions to that for
migrating the user info.
Let me know what you think.
-Jeff
17 years, 10 months
package containing ChangeLog -- switch to -common?
by Chris Weyl
Hey Dan,
What do you think of moving the ChangeLog to the plague-common
package, rather than the plague (server) package? That way one could
upgrade the -common and -client packages on their workstation first
and see what's changed, before upgrading the server.
Thanks-
-Chris
17 years, 10 months
Plague and other distros...
by Chris Weyl
Hey all --
Just a quick update, for those that are curious :)
RHEL -- This builds w/o issue under plague, mock configs are trivial.
Two things: you'll need to create your own yum repso; in rhel 3,
runuser needs to be set to '/bin/su'.
Mandrake -- Again, yum repos need to be built (if anyone knows of any
public repos with the base os and updates, I'd be much obliged).
Ditch the "delta" rpms when generating, they'll just mess things up
(for our purposes). I've been working with mandriva 2006.0.
'runuser' also needs to be set to '/bin/su' here.
For whatever reason (that I haven't been fully able to deduce), I've
found that the "checking for installed but unpackaged files" bit fails
horribly under mdk. For mdk spec files (and problematic rhel ones),
replacing that macro with this will help:
%define __check_files /bin/sh -c "(export TMPDIR=%{_tmppath} ; cd
%{_builddir}; /usr/lib/rpm/check-files %{buildroot})"
CVS integration works nicely as well -- make plague, make tag, etc,
all work nicely if you tweak CVSROOT/branches to include the rhel/mdk
distros. There are some functions that are fedora-hardcoded in
Makefile.common (e.g. "make mock"), but the basics work w/o tinkering.
One issue I am noting is that at the top/bottom of build.log's from
rhel, I often find 3-7 lines of:
error: Macro % has illegal name (%define)
error: Macro % has illegal name (%define)
etc, etc
I'm not entirely sure what's causing this. The build looks to
complete successfully (with resulting rpms to show for it), but
plague/mock claims it failed, so this is a bit of a problem.
Anyways... for the curious :) Basic upshot is that I haven't found
any changes that need to be made to plague proper, and 99% of it is
finding/generating yum repositories and tweaking mock config files.
-Chris
17 years, 10 months
mock configs for other flavors?
by Chris Weyl
Hey all--
Before I go about reinventing the wheel, does anyone have (or can
point me to) sample mock config files for RHEL3/4?
I'm also carrying on a rather spiritied conversation about using
plague to build for other distros (e.g. mandrake) over here, and would
love to be able to prove them wrong:) So, really, mock configs for
any flavor/distro would be most appreciated...
Thanks-
-Chris
17 years, 10 months
Build system maintenance complete
by Dan Williams
Hi,
I've updated and restarted the build system this morning to fix issues
many of you may have noticed with jobs stuck in downloading/done state.
Things should be flowing more smoothly now.
The problem was caused by plague using blocking sockets for RPM
downloads, which weren't playing well with SSL and firewall/iptables on
the builders. We now use non-blocking sockets with timeouts for RPM
downloads, and retry downloads up to 5 times before failing the job.
If you notice your job sitting in downloading/done for more than 10 or
15 minutes (it's normal to be in that state for a short time), please
email me the job # and I'll look at the logs to see what really went on
and hopefully fix it.
Thanks for the patience.
Dan
17 years, 10 months
Extras buildsystem back up
by Jeremy Katz
The Fedora Extras buildsystem is now back up. Apologies for the
downtime. There were some new firewall rules put into place which
didn't play well as well as one of the build machines booting into an
older, non-working kernel. Things should be back to normal now.
Additionally, the problems with uploading new tarballs to CVS should be
corrected. This was caused by a change in a mod_ssl errata
Thanks for your patience,
Jeremy
17 years, 10 months
Hrm, SSL issues?
by Chris Weyl
Ok, so this is probably something trivial, but I've been seeing these
SSL errors. I don't know if it had to do with the recent plague
updates or something else on this system (I'd imagine not, as it's
dedicated to the buildsys), but it's rather perplexing. It seems to
be referring to an expired cert, but after peeking at the certs all of
them seem to expire in 2015.
>From the client side:
-----------------------------
[cweyl@twink FC-3]$ plague-client list
Traceback (most recent call last):
File "/usr/bin/plague-client", line 420, in ?
cli = PlagueClient(os.path.expanduser(cfg_file))
File "/usr/bin/plague-client", line 85, in __init__
self._check_api_version(self._server)
File "/usr/bin/plague-client", line 90, in _check_api_version
server_ver = server.api_version()
File "/usr/lib/python2.4/xmlrpclib.py", line 1096, in __call__
return self.__send(self.__name, args)
File "/usr/lib/python2.4/xmlrpclib.py", line 1383, in __request
verbose=self.__verbose
File "/usr/lib/python2.4/xmlrpclib.py", line 1129, in request
self.send_content(h, request_body)
File "/usr/lib/python2.4/xmlrpclib.py", line 1243, in send_content
connection.endheaders()
File "/usr/lib/python2.4/httplib.py", line 794, in endheaders
self._send_output()
File "/usr/lib/python2.4/httplib.py", line 675, in _send_output
self.send(msg)
File "/usr/lib/python2.4/httplib.py", line 654, in send
self.sock.sendall(str)
File "/usr/lib/python2.4/site-packages/plague/SSLConnection.py",
line 79, in sendall
return self.__dict__["conn"].sendall(data, flags)
OpenSSL.SSL.Error: [('SSL routines', 'SSL3_GET_SERVER_CERTIFICATE',
'certificate verify failed')]
>From the server side:
------------------------------
Exception happened during processing of request from ('xx.xx.xx.xx', 59214)
Traceback (most recent call last):
File "/usr/lib/python2.4/SocketServer.py", line 463, in
process_request_thread self.finish_request(request, client_address)
File "/usr/lib/python2.4/SocketServer.py", line 254, in finish_request
self.RequestHandlerClass(request, client_address, self)
File "/usr/lib/python2.4/SocketServer.py", line 521, in __init__
self.handle()
File "/usr/lib/python2.4/BaseHTTPServer.py", line 314, in handle
self.handle_one_request()
File "/usr/lib/python2.4/BaseHTTPServer.py", line 297, in handle_one_request
self.raw_requestline = self.rfile.readline()
File "/usr/lib/python2.4/socket.py", line 340, in readline
data = self._sock.recv(self._rbufsize)
File "/usr/lib/python2.4/site-packages/plague/SSLConnection.py",
line 97, in recv
return self.__dict__["conn"].recv(bufsize, flags)
Error: [('SSL routines', 'SSL3_READ_BYTES', 'sslv3 alert certificate
expired'), ('SSL routines', 'SSL3_READ_BYTES', 'ssl handshake
failure')]
----------------------------------------
Any thoughts? Google isn't turning up anything that looks useful.
-Chris
17 years, 10 months
Extras buildsystem down
by Dan Williams
Hi,
All builders in the Extras buildsystem are currently unreachable by the
build server, due to errors in firewall rules that we're currently
fixing, plus prelink screwed up the PPC builder's pcre & grep, which are
being fixed. Please hang on while we correct the situation. No
requeueing of jobs should be necessary as they will automatically start
when the builders come back up.
Thanks!
Dan
17 years, 10 months
