November 2010 - buildsys - Fedora Mailing-Lists

by Jinze Xue

Actually,what I want to ask is how to build from SCM? the commend or the configs. I searched SCM on the internet , but no answer. Any help? thanks!!! 2010/11/19 <buildsys-request(a)lists.fedoraproject.org> > Send buildsys mailing list submissions to > buildsys(a)lists.fedoraproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://admin.fedoraproject.org/mailman/listinfo/buildsys > or, via email, send a message with subject or body 'help' to > buildsys-request(a)lists.fedoraproject.org > > You can reach the person managing the list at > buildsys-owner(a)lists.fedoraproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of buildsys digest..." > > > Today's Topics: > > 1. koji (Jinze Xue) > 2. Re: koji (Alan Franzoni) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 18 Nov 2010 20:55:42 +0800 > From: Jinze Xue <xuejinze(a)gmail.com> > Subject: koji > To: buildsys(a)lists.fedoraproject.org > Message-ID: > <AANLkTi=nsebhqDTsiXmOVDCKXt5nLEU=d-JQsUisG9BV(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > A question , > How to build from SCM? > thanks! > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.fedoraproject.org/pipermail/buildsys/attachments/20101118/9b... > > ------------------------------ > > Message: 2 > Date: Fri, 19 Nov 2010 11:09:15 +0100 > From: Alan Franzoni <mailing(a)franzoni.eu> > Subject: Re: koji > To: Discussion of Fedora build system > <buildsys(a)lists.fedoraproject.org> > Message-ID: > <AANLkTikFPQnTnHcBYz_rGndBDj1cAbSfo60mskth1P8q(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On Thu, Nov 18, 2010 at 1:55 PM, Jinze Xue <xuejinze(a)gmail.com> wrote: > > A question , > > ?How to build from SCM? > > I think there's no single answer to this question. I'll give you some > hints on what we do where I work. > > Currently the RPM system is designed to build from a source rpm, > period. Hence, you need to build a source RPM and feed it into mock or > koji. > > We've usually got a .spectemplate file on our SCM. This file contains > some tags, for example you can have something like ${SVN_REV} which is > then inserted in the .spectemplate as this: > > Release: svn${SVN_REV} > > > Once the CI system has tested an SCM revision and it's good, it packs > the contents of such revision, takes the spectemplate, substitues > variable and creates a .spec file, which is then feeded to mock/koji > for srpm building. That .src.rpm then gets built again by mock/koji. > > What's strange is that we actually need two build phases; the first is > done by the CI server, then there's a rebuild by mock or koji. It may > not be the fastest way to do it but it currently works. > > > -- > Alan Franzoni > -- > contact me at public(a)[mysurname].eu > > > ------------------------------ > > -- > buildsys mailing list > buildsys(a)lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/buildsys > > End of buildsys Digest, Vol 69, Issue 14 > **************************************** >

13 years, 4 months

3
2
0 / 0

How to split a install DVD to some CDs

by Eric Zhong

I have a install DVD, and i want split it to some install CDs, how to do ? I build some CDs use revisor , but when i replace the install.img , initrd.img and bootlogo in first CD, only first CD be installed, it will not to let you inseart the others. So, if i can modify the first CD the better. Or, split form DVD. Thanks.

13 years, 5 months

1
0
0 / 0

koji

by Jinze Xue

A question , How to build from SCM? thanks!

13 years, 5 months

2
1
0 / 0

koji

by Jinze Xue

hello when a system version update ,for example,f11 to f12, how were packages with release fc11 changed to fc12? I create new build tag new target and change the release package in the group of the build tag,but when I build a package ,it says the release of build and the release of rpms is different . so ,I can build the rpms out ,but I can't submit builds to the database,failed, any help ? thanks

13 years, 5 months

2
1
0 / 0

koji import error

by Vijay N. Majagaonkar

Hi All, Something new came up on my box today it was working correctly till yesterday, i have import packages and it successfully imported, but when rebuilt this package and trying import package i got the following error. now it's same with any package that i am trying to import it's not working. did some one came across this issue ? [shell] $ koji import spin-kickstarts-0.10.3-4.bcopa5.36.src.rpm uploading spin-kickstarts-0.10.3-4.bcopa5.36.src.rpm... done importing spin-kickstarts-0.10.3-4.bcopa5.36.src.rpm... Fault: <Fault 1: "<class 'pg.DatabaseError'>: error 'ERROR: value too long for type character varying(32)\n' in 'INSERT INTO rpmfiles (rpm_id,filename,filesize,filemd5,fileflags)\n VALUES (14578,'kscongif.ks',6340,'d0bdf6a193f0d202ebaf1631b94832c712b01a061e1f040966c9f4ce8f11f6ef',0)\n '"> [/shell] Thanks for the help Vijay.

13 years, 5 months

1
0
0 / 0

request

by Jinze Xue

hello! I want to build some rpms in fedora's build system ,can I be a user of fedora koji?or fedora sparc koji? thanks!

13 years, 5 months

2
1
0 / 0

How to regen install.img ?

by Eric Zhong

I want to know whether the pics in fedora-logos be put into install.img when generate iso by pungi ? After i replace pics in fedora-logos with mine , the pics during installation is also fedora's. How can i regen the install.img ?

13 years, 5 months

3
2
0 / 0

build error in koji

by steve.webb＠beatport.com

Hey there. I got my own koji server up and running, but builds seem to be failing. Here's the errors that I'm seeing: 19 build (dist-foo, less-436-2.el5.src.rpm): open (kojibuilder1) -> FAILED: BuildrootError: could not init mock buildroot, mock exited with status 20; see root.log for more information The root.log shows: INFO backend.py:747: Mock Version: 1.1.6 DEBUG backend.py:242: rootdir = /var/lib/mock/dist-foo-build-2-5/root/ DEBUG backend.py:243: resultdir = /var/lib/mock/dist-foo-build-2-5/result DEBUG backend.py:249: create skeleton dirs DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/var/lib/rpm DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/var/lib/rpm DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/var/lib/yum DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/var/lib/yum DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/var/lib/dbus DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/var/lib/dbus DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/var/log DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/var/log DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/var/lock/rpm DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/var/lock/rpm DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/etc/rpm DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/etc/rpm DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/tmp DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/tmp DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/var/tmp DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/var/tmp DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/etc/yum.repos.d DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/etc/yum.repos.d DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/etc/yum DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/etc/yum DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/proc DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/proc DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/sys DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/sys DEBUG backend.py:267: touch required files DEBUG util.py:68: touching file: /var/lib/mock/dist-foo-build-2-5/root/etc/mtab DEBUG util.py:68: touching file: /var/lib/mock/dist-foo-build-2-5/root/etc/fstab DEBUG util.py:68: touching file: /var/lib/mock/dist-foo-build-2-5/root/var/log/yum.log DEBUG backend.py:275: configure yum DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/etc DEBUG util.py:82: remove tree: /var/lib/mock/dist-foo-build-2-5/root/dev DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/dev/pts DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/dev/pts DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/dev/shm DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/dev/shm DEBUG backend.py:647: mount -n -t proc mock_chroot_proc /var/lib/mock/dist-foo-build-2-5/root/proc DEBUG util.py:301: Executing command: mount -n -t proc mock_chroot_proc /var/lib/mock/dist-foo-build-2-5/root/proc DEBUG util.py:340: Child returncode was: 0 DEBUG backend.py:647: mount -n -t sysfs mock_chroot_sysfs /var/lib/mock/dist-foo-build-2-5/root/sys DEBUG util.py:301: Executing command: mount -n -t sysfs mock_chroot_sysfs /var/lib/mock/dist-foo-build-2-5/root/sys DEBUG util.py:340: Child returncode was: 0 DEBUG backend.py:647: mount -n -t devpts -o gid=5,mode=0620,ptmxmode=0666,newinstance mock_chroot_devpts /var/lib/mock/dist-foo-build-2-5/root/dev/pts DEBUG util.py:301: Executing command: mount -n -t devpts -o gid=5,mode=0620,ptmxmode=0666,newinstance mock_chroot_devpts /var/lib/mock/dist-foo-build-2-5/root/dev/pts DEBUG util.py:340: Child returncode was: 0 DEBUG backend.py:647: mount -n -t tmpfs mock_chroot_shmfs /var/lib/mock/dist-foo-build-2-5/root/dev/shm DEBUG util.py:301: Executing command: mount -n -t tmpfs mock_chroot_shmfs /var/lib/mock/dist-foo-build-2-5/root/dev/shm DEBUG util.py:340: Child returncode was: 0 DEBUG backend.py:680: /usr/bin/yum --installroot /var/lib/mock/dist-foo-build-2-5/root/ groupinstall build DEBUG util.py:301: Executing command: /usr/bin/yum --installroot /var/lib/mock/dist-foo-build-2-5/root/ groupinstall build DEBUG util.py:340: Child returncode was: 0 DEBUG util.py:301: Executing command: umount -n /var/lib/mock/dist-foo-build-2-5/root/dev/shm DEBUG util.py:340: Child returncode was: 0 DEBUG util.py:301: Executing command: umount -n /var/lib/mock/dist-foo-build-2-5/root/dev/pts DEBUG util.py:340: Child returncode was: 0 DEBUG util.py:301: Executing command: umount -n /var/lib/mock/dist-foo-build-2-5/root/sys DEBUG util.py:340: Child returncode was: 0 DEBUG util.py:301: Executing command: umount -n /var/lib/mock/dist-foo-build-2-5/root/proc DEBUG util.py:340: Child returncode was: 0 DEBUG util.py:102: kill orphans - Steve Webb -- Steve Webb | System Administrator Beatport | Music for DJ's ------------------------------------------ 2399 Blake Street, Suite 170 Denver, Colorado USA 80205 tel: +1.720.932.9103 fax: +1.720.932.9104 noc: +1.303.565.2710 mobile: +1.303.564.4269

13 years, 5 months

2
4
0 / 0

"Pungi" vs "UBLinux" vs "Gartersnake"

by Narendra Sisodiya

I found 3 procedures to create ISO of a rpm based distro. I want to choose a procedure which give me maximum flexibility of customizations. So, I want a comparison between Pungi - https://fedorahosted.org/pungi/ vs UBLinux - http://wings.buffalo.edu/computing/ublinux/HOWTO-selectpkg.html vs Gartersnake - http://clpdk.hg.sourceforge.net/hgweb/clpdk/gartersnake/file/c916c50a6e66 -- ┌─────────────────────────┐ │ Narendra Sisodiya │ http://narendrasisodiya.com └─────────────────────────┘

13 years, 5 months

2
1
0 / 0

Mock exception on umount

by David Hrbáč

Hi, I'm trying to build packages with mock 1.0.12. I use this script: for i in {4-x86_64,4-i386,5-x86_64,5-i386}; do mock -r centos-$i syslinux-4.03-0.pre5.el5.hrb.src.rpm --resultdir=./syslinux/"%(dist)s"/"%(target_arch)s"/; done to produce my rpms. With chroots based on RHEL4.x/CentOS4.x I'm getting this error. With 5.x tree it is fine. INFO: Mock Version: 1.0.12 INFO: mounting tmpfs. INFO: enabled root cache INFO: enabled yum cache State Changed: cleaning yum metadata INFO: enabled ccache State Changed: running yum State Changed: creating cache State Changed: setup State Changed: build INFO: unmounting tmpfs. ERROR: Exception(syslinux-4.03-0.pre5.el5.hrb.src.rpm) Config(centos-4-i386) 1 minutes 40 seconds INFO: Results and/or logs in: ./syslinux/el4/i386/ INFO: Cleaning up build root ('clean_on_failure=True') State Changed: lock buildroot State Changed: clean Traceback (most recent call last): File "/usr/sbin/mock", line 743, in ? main(retParams) File "/usr/sbin/mock", line 685, in main do_rebuild(config_opts, chroot, args) File "<peak.util.decorators.rewrap wrapping __main__.do_rebuild at 0x2B507B3E5AA0>", line 3, in do_rebuild File "/usr/lib/python2.4/site-packages/mock/trace_decorator.py", line 70, in trace result = func(*args, **kw) File "/usr/sbin/mock", line 432, in do_rebuild chroot.clean() File "<peak.util.decorators.rewrap wrapping mock.backend.clean at 0x2B5077D12F50>", line 3, in clean File "/usr/lib/python2.4/site-packages/mock/trace_decorator.py", line 70, in trace result = func(*args, **kw) File "/usr/lib/python2.4/site-packages/mock/backend.py", line 141, in clean self._unlock_and_rm_chroot() File "<peak.util.decorators.rewrap wrapping mock.backend._unlock_and_rm_chroot at 0x2B5077D15488>", line 3, in _unlock_and_rm_chroot File "/usr/lib/python2.4/site-packages/mock/trace_decorator.py", line 70, in trace result = func(*args, **kw) File "/usr/lib/python2.4/site-packages/mock/backend.py", line 153, in _unlock_and_rm_chroot mock.util.rmtree(t, selinux=self.selinux) File "<peak.util.decorators.rewrap wrapping mock.util.rmtree at 0x2B5077D060C8>", line 3, in rmtree File "/usr/lib/python2.4/site-packages/mock/trace_decorator.py", line 70, in trace result = func(*args, **kw) File "/usr/lib/python2.4/site-packages/mock/util.py", line 87, in rmtree shutil.rmtree(path, *args, **kargs) File "/usr/lib64/python2.4/shutil.py", line 163, in rmtree rmtree(fullname, ignore_errors, onerror) File "/usr/lib64/python2.4/shutil.py", line 172, in rmtree onerror(os.rmdir, path, sys.exc_info()) File "/usr/lib64/python2.4/shutil.py", line 170, in rmtree os.rmdir(path) OSError: [Errno 16] Device or resource busy: '/var/lib/mock/centos-4-i386.tmp/root' After building I can see: [root@builder2 mock]# lsof | grep mock udevd 14726 root cwd DIR 0,24 40 504796 /var/lib/mock/centos-4-i386.tmp/root udevd 14726 root rtd DIR 0,24 40 504796 /var/lib/mock/centos-4-i386.tmp/root udevd 14726 root txt REG 0,24 11024 525683 /var/lib/mock/centos-4-i386.tmp/root/sbin/udevd (deleted) udevd 14726 root DEL REG 0,24 512893 /var/lib/mock/centos-4-i386.tmp/root/lib/libselinux.so.1 udevd 14726 root DEL REG 0,24 512658 /var/lib/mock/centos-4-i386.tmp/root/lib/tls/libc-2.3.4.so udevd 14726 root DEL REG 0,24 512583 /var/lib/mock/centos-4-i386.tmp/root/lib/ld-2.3.4.so udevd 14726 root 0u CHR 1,3 504826 /var/lib/mock/centos-4-i386.tmp/root/dev/null (deleted) udevd 14726 root 1u CHR 1,3 504826 /var/lib/mock/centos-4-i386.tmp/root/dev/null (deleted) udevd 14726 root 2u CHR 1,3 504826 /var/lib/mock/centos-4-i386.tmp/root/dev/null (deleted) There remains udevd running and I'm not able to delete the chroot folder even as root. [root@builder2 mock]# rm /var/lib/mock/* -rf; rm /var/cache/mock/* -rf rm: cannot remove directory `/var/lib/mock/centos-4-i386.tmp/root': Device or resource busy Any hints? Thanks, David Hrbáč

13 years, 5 months

5
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

buildsys November 2010