buildsys November 2006

buildsys@lists.fedoraproject.org

23 participants
23 discussions

buildsys misconfigured
by Michael Schwendt 25 Dec '06

25 Dec '06

FC-6]$ make build /usr/bin/plague-client build SDL_image SDL_image-1_2_5-2_fc6 fc6 Package SDL_image enqueued. Job ID: 22289. > http://buildsys.fedoraproject.org/build-status/job.psp?uid=22289 22289: SDL_image-1.2.5-2.fc7 (building) Where does the .fc7 come from? This is the FC-6 branch!

5 13

automate rpm signing?
by Douglas Hubler 20 Dec '06

20 Dec '06

The Fedora website http://fedora.redhat.com/About/security/ mentions Fedora builds are automatically signed. How is this done? rpm --addsign requires user input and is not gpg-aware http://lists.gnupg.org/pipermail/gnupg-users/2004-January/021302.html

6 9

Initial EPEL mock config
by Josh Boyer 16 Dec '06

16 Dec '06

Hi All, Below is an initial EPEL config. I'm not quite sure where packages will go, and I'm not sure if the CentOS base and updates are correct but I thought I would get this discussion started since EPEL is starting to move. Please review and let me know your thoughts. Again, this is just an example for now. thx, josh #!/usr/bin/python -tt import os config_opts['root'] = 'epel-4-i386' config_opts['target_arch'] = 'i386' config_opts['yum.conf'] = """ [main] cachdir=/var/cache/yum debuglevel=1 logfile=/var/log/yum.log reposdir=/dev/null retries=20 obsoletes=1 gpgcheck=0 assumeyes=1 # repos [core] name=base mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch… [update] name=updates mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch… [groups] name=groups baseurl=http://buildsys.fedoraproject.org/buildgroups/rhel4/i386/ [extras] name=epel mirrorlist=http://fedora.redhat.com/download/mirrors/epel-4 [local] name=local baseurl=http://buildsys.fedoraproject.org/plague-results/epel-4/

3 6

Using mock with SuSE Linux Enterprise Desktop?
by John Villalovos 06 Dec '06

06 Dec '06

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

4 5

Patch to buildsys-build.spec to support SuSE SLES
by John Villalovos 06 Dec '06

06 Dec '06

Attached is a patch which adds support for SuSE Linux Enterprise Server (SLES) to the buildsys-build.spec file. It is kind of ugly, since they use a lot of RPMS in their build environment. I haven't tried to trim it. I used the information from Matt Domsch that he has posted at http://linux.dell.com/files/mock/buildgroups/sles10/i386/ I hope this is useful for others. John

2 1

plague-client list
by Michael Schwendt 26 Nov '06

26 Nov '06

$ 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)

4 3

anaconda-runtime requirements
by Jarosław Górny 26 Nov '06

26 Nov '06

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

2 1

Truncated x86_64 build results from hammer2
by Michael Schwendt 25 Nov '06

25 Nov '06

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

1 0

plague-client detail <jobid>
by Michael Schwendt 25 Nov '06

25 Nov '06

Is this supposed to read "Status: needsign/success"? $ plague-client detail 22289 Detail for Job ID 22289 (SDL_image): -------------------------------------------------------------------------------- Source: SDL_image-1_2_5-2_fc6 Target: fedora-6-extras Submitter: bugs.michael(a)gmx.net Status: needsign/ Archjobs: i386: hammer2.fedora.redhat.com done/done x86_64: xenbuilder1.fedora.redhat.com done/done ppc: ppc3.fedora.redhat.com done/done

1 0

Pungi & seperating needed RPMs for Anaconda / Installation?
by Jeroen Janssen 23 Nov '06

23 Nov '06

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

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

buildsys November 2006