Re: [Errno 10] No child processes

2009-09-13 Thread
Hi, xiao li

This is very normally error.

Maybe some configure is wrong, create a builder, it have
configure look like following:

---
[r...@builder4-x86 ~]# grep mockdir /etc/kojid/kojid.conf
mockdir=/dist/mock
[r...@builder4-x86 ~]# ll -d /dist/mock/
drwxrwsr-x 6 root mock 4096 09-14 09:31 /dist/mock/
[r...@builder4-x86 ~]# grep mock /etc/group
mock:x:110:kojibuilder
[r...@builder4-x86 ~]# grep kojibuilder /etc/passwd
kojibuilder:x:101:107::/builddir:/bin/bash
[r...@builder4-x86 ~]# grep kojibuilder /etc/group
mock:x:110:kojibuilder
kojibuilder:x:107:
=

1.  must have kojibuilder user and mock group

2.  kojibuilder must have privileges to mockdir

a chinese help maybe found on my wiki :
http://jianlee.ylinux.org/Computer/%E6%9C%8D%E5%8A%A1%E5%99%A8/koji.html#sec64



2009/9/11 xiao li lixiao...@gmail.com:
 When I build srpm.I met a problem.It shows errno 10 and no child
 processes.The log follows,
  'Traceback (most recent call last):\n  File /usr/sbin/kojid, line 1275,
 in runTask\n    response = (handler.run(),)\n  File /usr/sbin/kojid, line
 1351, in run\n    return self.handler(*self.params,**self.opts)\n  File
 /usr/sbin/kojid, line 2009, in handler\n    broot.init()\n  File
 /usr/sbin/kojid, line 467, in init\n    rv = self.mock([\'--init\'])\n
 File /usr/sbin/kojid, line 389, in mock\n    status = os.waitpid(pid,
 os.WNOHANG)\nOSError: [Errno 10] No child processes\n'
  Thanks for your help.




-- 
Jian Lee  [ http://jianlee.ylinux.org ]

--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list


Re: Fedora-buildsys-list Digest, Vol 54, Issue 5

2009-08-18 Thread
Sometimes, it because your postgresql setting have error:

on my host, /etc/koji-hub/hub.conf have some info:

  3 ## Basic options ##
  4 DBName = koji
  5 DBUser = koji
  6 DBHost = 127.0.0.1
  7 DBPass = password for user koji login datebase koji from 127.0.0.1
==

good luck.




2009/8/18, lixiao-a lixia...@163.com:

 Hi,
 I have a koji server running locally at my workplace.
 Recently, I am unable to execute some koji cli commands. I get the
 following error:

 [kojiad...@linux-dev koji]$ koji add-user kojira
 ServerOffline: database outage,anyone can help me?Thanks.


 --
 没有广告的终身免费邮箱,www.yeah.net http://www.yeah.net/?from=footer
 --
 Fedora-buildsys-list mailing list
 Fedora-buildsys-list@redhat.com
 https://www.redhat.com/mailman/listinfo/fedora-buildsys-list




-- 
李建

主页  http://jianlee.ylinux.org
msn   lijian@gmail.com
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

Re: Fedora-buildsys-list Digest, Vol 52, Issue 2

2009-06-03 Thread
I just solved this problem, and I send to maillist. You can search it!

2009/6/3 lixiao-a lixia...@163.com

 Thanks for your help ,but I still have the problem.I copied the virtual
 machines to a new PC.so the yum depository still visit the old IP.So the
 mock buildroot init has error.How to make it visit the new IP?Could you help
 me?


 --
 网易全新推出企业邮箱 http://qiye.163.com/?ft=2
 --
 Fedora-buildsys-list mailing list
 Fedora-buildsys-list@redhat.com
 https://www.redhat.com/mailman/listinfo/fedora-buildsys-list




-- 
李建
msn  lijian@gmail.com
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

Re: When I modified the koji server'ip from one to another, the yum use the old ip already!

2009-06-03 Thread
Good,the method you give is simple.I'll test later.My repo table in sql now
is following,Did you can tell me what's mean about state=3 ? and state=1
,and state=2 ?

Thank you very much ! I have draw a koji illustrative diagram , can you give
me some advices?

http://workplace.turbolinux.com.cn/attachments/120/koji%E5%8E%9F%E7%90%86%E5%9B%BE.png
**

I've write many docs about install koji server and use koji,all is chinese.
Can I put it on koji wiki ?

https://fedoraproject.org/wiki/Talk:Koji


koji= SELECT * from repo;
 id | create_event | tag_id | state
+--++---
  5 | 3848 |  2 | 3
  6 | 3849 |  2 | 3
  8 | 3860 |  1 | 3
  7 | 3857 |  2 | 3
  9 | 3861 |  2 | 3
 10 | 3883 |  2 | 3
 11 | 3899 |  2 | 3
 12 | 3901 |  2 | 3
 13 | 3982 |  2 | 3
 14 | 4021 |  2 | 3
 15 | 4044 |  2 | 3
 16 | 4073 |  2 | 3
 17 | 4117 |  2 | 3
 18 | 4151 |  2 | 3
 19 | 4160 |  2 | 3
 20 | 4162 |  2 | 3
 21 | 4189 |  2 | 3
 22 | 4200 |  2 | 3
 23 | 4305 |  2 | 3
 24 | 4382 |  2 | 3
 25 | 4431 |  2 | 3
 27 | 4455 |  4 | 3
 28 | 4457 |  4 | 3
 29 | 4463 |  4 | 3
 30 | 4494 |  4 | 3
 31 | 4509 |  4 | 3
 32 | 4511 |  4 | 3
 33 | 4521 |  4 | 3
 34 | 4531 |  4 | 3
 40 | 7335 |  5 | 2
 41 | 7348 |  3 | 2
 42 | 7349 |  5 | 2
 35 | 4540 |  4 | 3
 43 | 7350 |  6 | 2
 45 | 7356 |  6 | 2
 46 | 7369 |  6 | 2
 44 | 7355 |  4 | 2
 47 | 7372 |  6 | 2
 48 | 7373 |  4 | 2
 49 | 7376 |  6 | 2
 52 | 7392 |  6 | 2
 56 | 7401 |  6 | 2
 50 | 7379 |  4 | 2
 51 | 7386 |  2 | 1
 26 | 4441 |  2 | 3
 53 | 7394 |  6 | 2
 54 | 7396 |  6 | 2
 57 | 7405 |  6 | 2
 59 | 7424 |  4 | 1
 55 | 7400 |  6 | 2
 36 | 7290 |  6 | 3
 37 | 7292 |  6 | 3
 38 | 7318 |  6 | 3
 39 | 7323 |  6 | 3
 58 | 7410 |  6 | 2
 61 | 7443 |  6 | 1
 60 | 7441 |  6 | 2
(57 rows)



2009/6/4 Mike McLean mi...@redhat.com

 李建 wrote:

 I've solv this probole. the /usr/sbin/kojid have following code:
 --
 2584 #cmd.append('--update')
 2585 #if options.createrepo_skip_stat:
 2586 #cmd.append('--skip-stat')
 ==

 I commented it , so the createrepo run as follow (see createrepo.log):


 It seems a little silly to comment out code that can be disabled with a
 configuration option (createrepo_skip_stat). Of course, there is no option
 to disable the --update.

 When I need to force the system to regenerate repos from scratch I just
 expire them in the db. This works because kojid will only recycle repodata
 from a repo in the READY state. Anyway, to expire all current repos, I'd use
 this sql command:
 - update repo set state = 2 where state in (0, 1);
 You'll also need to cancel any newRepo tasks that were running beforehand.

 --
 Fedora-buildsys-list mailing list
 Fedora-buildsys-list@redhat.com
 https://www.redhat.com/mailman/listinfo/fedora-buildsys-list




-- 
李建
msn  lijian@gmail.com
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

Re: How to remove the large directory after build ?

2009-06-01 Thread
Now ,the directory is:
-
[r...@localhost mock]# du -hs *
651Mgtes11.2-build-10-9
18M gtes11.2-build-13-10
5.6Mgtes11.2-build-15-15
549Mgtes11.2-build-1-6
5.5Mgtes11.2-build-16-15
18M gtes11.2-build-18-18
18M gtes11.2-build-19-18
579Mgtes11.2-build-21-20
560Mgtes11.2-build-22-20
3.5Ggtes11.2-build-23-26
548Mgtes11.2-build-2-6
567Mgtes11.2-build-3-6
583Mgtes11.2-build-5-9
562Mgtes11.2-build-6-9
670Mgtes11.2-build-9-9
6.2Mgtes11.3-build-24-28
6.1Mgtes11.3-build-25-28
637Mgtes11.3-build-26-30
609Mgtes11.3-build-28-30
3.5Ggtes11.3-build-30-30
3.0Ggtes11.3-build-31-30
1.8Ggtes11.3-build-32-32
1.8Ggtes11.3-build-34-32
583Mgtes11.3-build-35-33
562Mgtes11.3-build-37-33
888Mgtes11.3-build-39-34
852Mgtes11.3-build-40-34
408Mmoblin2-build-41-38
417Mmoblin2-build-42-39
539Mmoblin2-build-43-39
==


My builder is ok:

[r...@localhost mock]# koji list-hosts
Hostname Enb Rdy Load/Cap Arches   Last Update
kojibuilder1 N   N0.0/2.0 i386,x86_64  2009-05-25
19:08:25
kojibuilder2 Y   Y0.0/2.0 ia64 2009-05-29
14:18:59
kojibuilder3 Y   Y0.0/2.0 x86_64,i386  2009-06-02
10:09:00
==

Why ? Because I use a special disk space,and I use Selinux, So I modified
the /var/lib/mock to /dist/mock on kojihub and kojiweb and kojibuilder3
host. but the kojibuilder2's mock directory is /var/lib/mock ,a link to
/dist/mock on it's host.

the kojihub and kojiweb and kojibuilder3's /mnt/koji directory is modified
to /data/koji also . but the other kojibuilder*'s directory is /mnt/koji by
nfs mount.

Why ? It isn't change or removed after 1 days.

Thanks!


2009/6/1 Mike Bonnet mi...@redhat.com

 李建 wrote:

 Hello,everybody!

 My koji server has setup ok. but the mock dir is more and more large. How
 to
 remove it ?
 I mean if koji has this feature,I doesn't to do it myself. Is anyone can
 help me ?

 my mock directory info :
 
 651Mgtes11.2-build-10-9
 18M gtes11.2-build-13-10
 5.6Mgtes11.2-build-15-15
 549Mgtes11.2-build-1-6
 5.5Mgtes11.2-build-16-15
 18M gtes11.2-build-18-18
 18M gtes11.2-build-19-18
 579Mgtes11.2-build-21-20
 560Mgtes11.2-build-22-20
 3.5Ggtes11.2-build-23-26
 548Mgtes11.2-build-2-6
 567Mgtes11.2-build-3-6
 583Mgtes11.2-build-5-9
 562Mgtes11.2-build-6-9
 670Mgtes11.2-build-9-9
 6.2Mgtes11.3-build-24-28
 6.1Mgtes11.3-build-25-28
 637Mgtes11.3-build-26-30
 609Mgtes11.3-build-28-30
 3.5Ggtes11.3-build-30-30
 3.0Ggtes11.3-build-31-30
 1.8Ggtes11.3-build-32-32
 1.8Ggtes11.3-build-34-32
 583Mgtes11.3-build-35-33
 562Mgtes11.3-build-37-33
 888Mgtes11.3-build-39-34
 852Mgtes11.3-build-40-34
 408Mmoblin2-build-41-38
 417Mmoblin2-build-42-39
 ==


 kojid manages the cleanup up the /var/lib/mock directory for builds it
 runs.  Buildroots for successful builds will be cleaned up almost
 immediately.  Buildroots for unsuccessful builds will be cleaned up after 4
 hours, to give you a chance to debug the failure or copy relevant data out
 of the buildroot for later analysis.

 --
 Fedora-buildsys-list mailing list
 Fedora-buildsys-list@redhat.com
 https://www.redhat.com/mailman/listinfo/fedora-buildsys-list




-- 
李建
msn  lijian@gmail.com
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

Re: How to creating install images by koji ?

2009-05-10 Thread
Thanks also. May be.

I'll try to achieve this point . :)

2009/5/10 Jeroen van Meeuwen kana...@kanarip.com

 On 05/08/2009 04:14 AM, 李建 wrote:

 http://fedoraproject.org/wiki/Koji has said that koji can creating
 install images , but I have not find cmd yet .
 did anyone can help me ?


 I think the terminology used here is a little off...

 Kojid as a daemon is actually responsible for triggering an application
 called 'mock' using all the correct parameters and configuration for a
 certain type of build. As such, it is responsible (through mock) for
 creating the clean build chroot and triggering the build of a RPM package,
 not necessarily for creating the installer images that make a set of CDs or
 the DVD perform the installation of Fedora.

 Hope this helps,

 Kind regards,

 Jeroen van Meeuwen
 -kanarip

 --
 Fedora-buildsys-list mailing list
 Fedora-buildsys-list@redhat.com
 https://www.redhat.com/mailman/listinfo/fedora-buildsys-list




-- 
李建
msn  lijian@gmail.com
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

How to do when build x86_64 pkgs needed i386 pkgs, but i386 pkgs have some files contented in x86_64 pkgs ?

2009-05-07 Thread
I've setup a koji server myself,and import all rpms and srpms into database.
Created tags,targets,buildhost,everything is ok.but when i build pkgs for
x86_64,There is dependence about i386 pkgs. I've modified mock code ,and
solve this problems . but a new question appear.

I have a problem when build x86_64 pkgs, the root.log is :
-

DEBUG backend.py:554:  /usr/bin/yum --installroot
/var/lib/mock/gtes-11-build-76-155/root/  install  'libtermcap-devel'
'pam-devel' 'perl'
DEBUG util.py:280:  Executing command: /usr/bin/yum --installroot
/var/lib/mock/gtes-11-build-76-155/root/  install  'libtermcap-devel'
'pam-devel' 'perl'
DEBUG util.py:256:
=
DEBUG util.py:256:   Package Arch   Version
  RepositorySize
DEBUG util.py:256:
=
DEBUG util.py:256:  Installing:
DEBUG util.py:256:   libtermcap-develi386   2.0.8-46.1
  build  51 k
DEBUG util.py:256:   libtermcap-develx86_64 2.0.8-46.1
  build  51 k
DEBUG util.py:256:   pam-devel   i386   0.99.6.2-4
  build 146 k
DEBUG util.py:256:   pam-devel   x86_64 0.99.6.2-4
  build 146 k
DEBUG util.py:256:  Installing for dependencies:
DEBUG util.py:256:   audit-libs  i386   1.7.7-6
  build  64 k
DEBUG util.py:256:   cracklibi386   2.8.9-3.1
  build  54 k
DEBUG util.py:256:   glibc   i686   2.5-34
  build 5.1 M
DEBUG util.py:256:   libselinux  i386   1.33.4-5.1
  build  43 k
DEBUG util.py:256:   libsepoli386   1.15.2-1
  build 106 k
DEBUG util.py:256:   libtermcap  i386   2.0.8-46.1
  build 9.3 k
DEBUG util.py:256:   pam i386   0.99.6.2-4
  build 941 k
DEBUG util.py:256:  Transaction Summary
DEBUG util.py:256:
=
DEBUG util.py:256:  Install 11 Package(s)
DEBUG util.py:256:  Update   0 Package(s)
DEBUG util.py:256:  Remove   0 Package(s)
DEBUG util.py:256:  Total download size: 6.7 M
DEBUG util.py:256:  Transaction Check Error:
DEBUG util.py:256:file /usr/share/man/man5/limits.conf.5.gz from
install of pam-0.99.6.2-4 conflicts with file from package
pam-0.99.6.2-4
DEBUG util.py:256:file /usr/share/man/man5/namespace.conf.5.gz
from install of pam-0.99.6.2-4 conflicts with file from package
pam-0.99.6.2-4
DEBUG util.py:256:file /usr/share/man/man8/pam_access.8.gz from
install of pam-0.99.6.2-4 conflicts with file from package
pam-0.99.6.2-4
DEBUG util.py:256:file /usr/share/man/man8/pam_cracklib.8.gz from
install of pam-0.99.6.2-4 conflicts with file from package
pam-0.99.6.2-4
DEBUG util.py:256:file /usr/share/man/man8/pam_lastlog.8.gz from
install of pam-0.99.6.2-4 conflicts with file from package
pam-0.99.6.2-4
DEBUG util.py:256:file /usr/share/man/man8/pam_limits.8.gz from
install of pam-0.99.6.2-4 conflicts with file from package
pam-0.99.6.2-4
DEBUG util.py:256:file /usr/share/man/man8/pam_namespace.8.gz from
install of pam-0.99.6.2-4 conflicts with file from package
pam-0.99.6.2-4
DEBUG util.py:256:file /usr/share/man/man8/pam_selinux.8.gz from
install of pam-0.99.6.2-4 conflicts with file from package
pam-0.99.6.2-4
DEBUG util.py:256:file /usr/share/man/man8/pam_succeed_if.8.gz
from install of pam-0.99.6.2-4 conflicts with file from package
pam-0.99.6.2-4
DEBUG util.py:256:file /usr/share/man/man8/pam_time.8.gz from
install of pam-0.99.6.2-4 conflicts with file from package
pam-0.99.6.2-4
DEBUG util.py:256:file /usr/share/man/man8/pam_tty_audit.8.gz from
install of pam-0.99.6.2-4 conflicts with file from package
pam-0.99.6.2-4
DEBUG util.py:256:  Error Summary
DEBUG util.py:256:  -
DEBUG util.py:319:  Child returncode was: 1

==

Any one can help me ?

-- 
李建
msn  lijian@gmail.com
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

I've a puzzle on koji when build x86_64 arch.

2009-05-07 Thread
I'just verify the
http://kojipkgs.fedoraproject.org/packages/rsh/0.17/54.fc11/data/logs/x86_64/root.log,
it issue

/usr/bin/yum --installroot
/var/lib/mock/dist-f11-build-415492-69017/root/  groupinstall build

just install x86_64 pkgs! but my project needed some i386 pkgs! I know
that rhel and centos
is needed i386 pkgs also. Why fedora's koji can ? My koji can't ! And
the previous questions i
posted is releated to this - I just added a pkglist content needed
i386 pkgs when create pkglist
for x86_64 arch.

Did anyone can help me ? Thanks!


-- 
李建
msn  lijian@gmail.com
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

Re: I've a puzzle on koji when build x86_64 arch.

2009-05-07 Thread
yes, I know koji doesn't support add i386 pkgs when build x86_64. And I
modified the kojihub.py to fixed this:
---
[r...@localhost ~]# diff /usr/share/koji-hub/kojihub.py
/dist/lab/koji/hub/kojihub.py
1788,1790d1787
 if arch == 'x86_64':
 for line in
file('/mnt/koji/repos/i386_pkg-needby-x86_64.list','r'):
 pkglist.write(line)
=

But,it have some problems when build some pkgs. I'll try the glibc32.

Thank you very much !

2009/5/8 Bryce br...@zeniv.linux.org.uk

 李建 wrote:
  I'just verify the
 
 http://kojipkgs.fedoraproject.org/packages/rsh/0.17/54.fc11/data/logs/x86_64/root.log
 ,
  it issue
 
  /usr/bin/yum --installroot
  /var/lib/mock/dist-f11-build-415492-69017/root/  groupinstall build
 
  just install x86_64 pkgs! but my project needed some i386 pkgs! I know
  that rhel and centos
  is needed i386 pkgs also. Why fedora's koji can ? My koji can't ! And
  the previous questions i
  posted is releated to this - I just added a pkglist content needed
  i386 pkgs when create pkglist
  for x86_64 arch.
 
  Did anyone can help me ? Thanks!
 
 
 
  
 
  --
  Fedora-buildsys-list mailing list
  Fedora-buildsys-list@redhat.com
  https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 I wonder if you're tripping over the same issues I had some time ago,
 you may need glibc32
 (http://koji.fedoraproject.org/koji/buildinfo?buildID=1160)

  Issue 2. One of the fun items in xen is that when you're building the
   64bit version there is an odd dependency on pulling in a 32bit
   glibc-devel by adding /usr/include/gnu/stubs-32.h to the dependency
   list, when building in x86_64 that dependancy cannot get satisfied.
 How
   can I beat the tag into realizing it can pull from the i386 repo to
   fulfill that requirement?
 

Fedora uses the glibc32 and glibc64 packages to provide these
dependencies.  A bit of a hack, but it works:

http://cvs.fedoraproject.org/viewcvs/rpms/glibc32/devel/
http://cvs.fedoraproject.org/viewcvs/rpms/glibc64/devel/

Koji won't let you pull i386 packages into a x86_64 build environment,
or vice versa.  The build environments are single-arch only.

 Where glibc32 is for x86_64 and glibc64 is for ppc64 if I recall
 correctly. A bit long in the tooth but that seems to be still current in
 koji best I can tel (course someone will now contradict me...)

 Phil
 =--=

 --
 Fedora-buildsys-list mailing list
 Fedora-buildsys-list@redhat.com
 https://www.redhat.com/mailman/listinfo/fedora-buildsys-list




-- 
李建
msn  lijian@gmail.com
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

How to creating install images by koji ?

2009-05-07 Thread
http://fedoraproject.org/wiki/Koji has said that koji can creating install
images , but I have not find cmd yet .
did anyone can help me ?

Thanks,

-- 
李建
msn  lijian@gmail.com
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

how init mock ? there are need some packages about i386 for build x86_64 packages !

2009-05-05 Thread
hello,everybody!

I've setup koji server , but i'm doubt how to set repo when some packages on
x86_64 need packages on i386 . when i run command on x86_64 system:
--
# koji build gtes-11 audit-1.7.7-6.el5_3.2.src.rpm --scratch


the root.log have erros :

--
DEBUG util.py:280:  Executing command: /usr/bin/yum --installroot
/var/lib/mock/gtes-11-build-13-15/root/  groupinstall build
DEBUG util.py:256:  Error: Missing Dependency: libgcc_s.so.1 is needed
by package gcc
DEBUG util.py:319:  Child returncode was: 1
DEBUG backend.py:542:  umount -n /var/lib/mock/gtes-11-build-13-15/root/proc
=

In my project , libgcc_s.so.1 is a file of libgcc-4.1.2-42.i386 。how to add
the repo info about libgcc-4.1.2-42.i386 on x86_64 system enviroment ?

Thanks!

-- 
Jian Lee
msn  lijian@gmail.com
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

Re: how init mock ? there are need some packages about i386 for build x86_64 packages !

2009-05-05 Thread
Thank you very much !

Nearly,I need an external repository . But i just want the mock can use
pkglist of i386 when build a package in x86_64 enviroment.
the default contents in /var/lib/mock/gtes-11-build-18-15/root/etc/yum.conf
are:
-
[main]
cachedir=/var/cache/yum
debuglevel=1
logfile=/var/log/yum.log
reposdir=/dev/null
retries=20
obsoletes=1
gpgcheck=0
assumeyes=1

# repos

[build]
name=build
baseurl=file:///mnt/koji/repos/gtes-11-build/15/x86_64
==

The first idea , I want the koji can auto add some contents follow when
build a package of x86_64 :
--
[addon]
name=addon
baseurl=file:///mnt/koji/repos/gtes-11-build/15/i386
==

I'll modify the code tomorrow and try again , Now get off work :)


2009/5/5 Steve Traylen st...@traylen.net

 2009/5/5 李建 lijian@gmail.com:
  hello,everybody!
 
  I've setup koji server , but i'm doubt how to set repo when some packages
 on
  x86_64 need packages on i386 . when i run command on x86_64 system:
  --
  # koji build gtes-11 audit-1.7.7-6.el5_3.2.src.rpm --scratch
  
 
  the root.log have erros :
 
  --
  DEBUG util.py:280:  Executing command: /usr/bin/yum --installroot
  /var/lib/mock/gtes-11-build-13-15/root/  groupinstall build
  DEBUG util.py:256:  Error: Missing Dependency: libgcc_s.so.1 is needed by
  package gcc
 
  DEBUG util.py:319:  Child returncode was: 1
  DEBUG backend.py:542:  umount -n
 /var/lib/mock/gtes-11-build-13-15/root/proc
  =
 
  In my project , libgcc_s.so.1 is a file of libgcc-4.1.2-42.i386 。how to
 add
  the repo info about libgcc-4.1.2-42.i386 on x86_64 system enviroment ?

 Sounds like you want to add an external repository?
 http://fedoraproject.org/wiki/Koji/ExternalRepoServerBootstrap
 Steve

 
  Thanks!
 
  --
  Jian Lee
  msn  lijian@gmail.com
 
 
  --
  Fedora-buildsys-list mailing list
  Fedora-buildsys-list@redhat.com
  https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 



 --
 Steve Traylen

 --
 Fedora-buildsys-list mailing list
 Fedora-buildsys-list@redhat.com
 https://www.redhat.com/mailman/listinfo/fedora-buildsys-list




-- 
李建
msn  lijian@gmail.com
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list