Using mock with SuSE Linux Enterprise Desktop?
by John Villalovos
Has anyone done any work using Mock with SuSE Linux Enterprise
Desktop? We are working on a project where we need to build RPMS for
Fedora, RHEL, SLED, and maybe OpenSuSE.
So Mock looked like a cool tool to use. I've got it working with
Fedora and have found info for RHEL/CentOS stuff.
I've found a little bit of info for SuSE but it looks like it was done
before Mock 0.5 came out.
Thanks for any info!
John
17 years
plague-client list
by Michael Schwendt
$ plague-client list
Error: an error ocurred communicating with the server.
'<Fault 1: 'pg.DatabaseError:error \'ERROR: expression too complex\nDETAIL: Nesting depth exceeds maximum expression depth 10000.\nHINT: Increase the configuration parameter "max_expr_depth".\n\' in \'SELECT jobid, parent_uid, starttime, endtime, arch, builder_addr, status, builder_status FROM archjobs WHERE
parent_uid=5
---snip--- (400K of parent_uid=...)
$ plague-client list status needsign
(same here)
$ plague-client list result success
(same here)
$ plague-client list status failed
Error: connection to the server timed out. '(110, 'Operation timed out.')'
$ plague-client list status building
(same here)
$ plague-client list email myemailaddress
(works)
17 years
anaconda-runtime requirements
by Jarosław Górny
Hi,
are there any reasons for anaconda-runtime requiring anaconda?
Because of this requirement, when I want to play with anaconda-runtime (eg.
pungi), I also have to install some completely unnecessary packages, like
libdhcp6client or pyparted.
regards,
--
Jaroslaw Gorny
17 years
Truncated x86_64 build results from hammer2
by Michael Schwendt
Build job 22303 (hammer2 for x86_64) produced a truncated x86_64 rpm:
http://buildsys.fedoraproject.org/build-status/job.psp?uid=22303
Should be above 5MiB in size, but is only 114688 bytes short:
$ rpm -Kv kile-1.9.3-1.fc3.1.x86_64.rpm
error: kile-1.9.3-1.fc3.1.x86_64.rpm: headerRead failed
$ stat kile-1.9.3-1.fc3.1.x86_64.rpm
File: `kile-1.9.3-1.fc3.1.x86_64.rpm'
Size: 114688 Blocks: 232 IO Block: 4096 regular file
Device: 811h/2065d Inode: 32325671 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 0/ root)
Access: 2006-11-25 17:38:08.000000000 -0500
Modify: 2006-11-25 12:15:34.000000000 -0500
Change: 2006-11-25 12:15:34.000000000 -0500
17 years
Pungi & seperating needed RPMs for Anaconda / Installation?
by Jeroen Janssen
Hi,
When building an installation CD with pungi, the packages needed for
Anaconda need to also be present in the 'repository'. (this is
probably generic for building an Anaconda installer?)
Is there a way to differentiate between RPMs that are needed for
Anaconda and the RPMs that should end up as 'installable' on the
disc?.
Example:
baseurl_anaconda=http://...FC6.url.../
baseurl=http://..MyOwn.url.../
Here 'baseurl_anaconda' is some place that Anaconda can get RPMs from
(the PACKAGES from Anaconda upd-instroot) and 'base_url' is the place
for 'installable' RPMs.
Any thoughts?
Best regards,
Jeroen Janssen
17 years