How to creating install images by koji ?
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
Re: I've a puzzle on koji when build x86_64 arch.
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
> 李建 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
Re: I've a puzzle on koji when build x86_64 arch.
李建 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
Re: mash fails for me with x86_64.
On Thu, May 7, 2009 at 4:00 PM, Bill Nottingham wrote: >> 2009-05-07 10:35:50 mash: Waiting for depsolve and createrepo to finish... >> 2009-05-07 10:35:50 mash: Resolving multilib for arch x86_64 using method >> devel >> Traceback (most recent call last): >> File "/usr/bin/mash", line 82, in >> main() >> File "/usr/bin/mash", line 70, in main >> rc = themash.doMultilib() >> File "/usr/lib/python2.5/site-packages/mash/__init__.py", line 513, >> in doMultilib >> pid = self.doDepSolveAndMultilib(arch, repocache) >> File "/usr/lib/python2.5/site-packages/mash/__init__.py", line 464, >> in doDepSolveAndMultilib >> yumbase.doTsSetup() >> File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 86, in >> doTsSetup >> return self._getTs() >> File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 101, in >> _getTs >> self._getTsInfo(remove_only) >> File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 112, >> in _getTsInfo >> pkgSack = self.pkgSack >> File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 592, in >> >> pkgSack = property(fget=lambda self: self._getSacks(), >> File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 435, >> in _getSacks >> self.repos.populateSack(which=repos) >> File "/usr/lib/python2.5/site-packages/yum/repos.py", line 251, in >> populateSack >> sack.populate(repo, mdtype, callback, cacheonly) >> File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 162, in >> populate >> if self._check_db_version(repo, mydbtype): >> File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 223, in >> _check_db_version >> return repo._check_db_version(mdtype) >> File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 1147, >> in _check_db_version >> repoXML = self.repoXML >> File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 1305, in >> >> repoXML = property(fget=lambda self: self._getRepoXML(), >> File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 1301, >> in _getRepoXML >> raise Errors.RepoError, msg >> yum.Errors.RepoError: Cannot retrieve repository metadata >> (repomd.xml) for repository: centos4-x86_64. Please >> verify its path and try again >> 2009-05-07 10:35:51 mash: Depsolve and createrepo finished. >> mash failed in out/centos4 >> >> Any ideas? > > Ugh. What's the temporary yum.conf that's created look like, if you > pull it out? Hi Bill, Thanks this was enough to spot the problem. The relative path "-o out" was not resolved at a certain point. Using a full path it proceeded. https://bugzilla.redhat.com/show_bug.cgi?id=499645 submitted. Many Thanks Steve > > You may want to just try rebuilding the F11 version and see if that > works for you. > > Bill > > -- > 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
Re: mash fails for me with x86_64.
> 2009-05-07 10:35:50 mash: Waiting for depsolve and createrepo to finish... > 2009-05-07 10:35:50 mash: Resolving multilib for arch x86_64 using method > devel > Traceback (most recent call last): > File "/usr/bin/mash", line 82, in > main() > File "/usr/bin/mash", line 70, in main > rc = themash.doMultilib() > File "/usr/lib/python2.5/site-packages/mash/__init__.py", line 513, > in doMultilib > pid = self.doDepSolveAndMultilib(arch, repocache) > File "/usr/lib/python2.5/site-packages/mash/__init__.py", line 464, > in doDepSolveAndMultilib > yumbase.doTsSetup() > File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 86, in > doTsSetup > return self._getTs() > File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 101, in _getTs > self._getTsInfo(remove_only) > File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 112, > in _getTsInfo > pkgSack = self.pkgSack > File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 592, in > > pkgSack = property(fget=lambda self: self._getSacks(), > File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 435, > in _getSacks > self.repos.populateSack(which=repos) > File "/usr/lib/python2.5/site-packages/yum/repos.py", line 251, in > populateSack > sack.populate(repo, mdtype, callback, cacheonly) > File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 162, in > populate > if self._check_db_version(repo, mydbtype): > File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 223, in > _check_db_version > return repo._check_db_version(mdtype) > File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 1147, > in _check_db_version > repoXML = self.repoXML > File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 1305, in > > repoXML = property(fget=lambda self: self._getRepoXML(), > File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 1301, > in _getRepoXML > raise Errors.RepoError, msg > yum.Errors.RepoError: Cannot retrieve repository metadata > (repomd.xml) for repository: centos4-x86_64. Please > verify its path and try again > 2009-05-07 10:35:51 mash: Depsolve and createrepo finished. > mash failed in out/centos4 > > Any ideas? Ugh. What's the temporary yum.conf that's created look like, if you pull it out? You may want to just try rebuilding the F11 version and see if that works for you. Bill -- 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.
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
mash fails for me with x86_64.
Hi, On F10. i.e mash-0.4.2-3.fc10.noarch createrepo-0.9.6-3.fc10.noarch yum-3.2.21-2.fc10.noarch I want to build a repo out of a koji-tag containing packages built against centos4. mash -c etc/mash.conf -o out centos4 Mash gives an error File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 1305, in repoXML = property(fget=lambda self: self._getRepoXML(), File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 1301, in _getRepoXML raise Errors.RepoError, msg yum.Errors.RepoError: Cannot retrieve repository metadata (repomd.xml) for repository: centos4-x86_64. Please verify its path and try again my centos4.conf contains [centos4] rpm_path = %(arch)s/ repodata_path = %(arch)s/ source_path = SRPMS debuginfo = Falsea multilib = True multilib_method = devel tag = dist-centos4 inherit = True strict_keys = False arches = x86_64 with only arches = i386 all is well , with arches = x86_64 or both it fails as above. It looks very similar to https://bugzilla.redhat.com/show_bug.cgi?id=350391 but that was fixed and released some time ago. Full python message: 2009-05-07 10:35:50 mash: Getting package lists for dist-centos4... 2009-05-07 10:35:50 mash: Sorting packages... 2009-05-07 10:35:50 mash: Checking signatures... 2009-05-07 10:35:50 mash: Writing out files for out/centos4/x86_64/... 2009-05-07 10:35:50 mash: Writing out files for out/centos4/SRPMS... 2009-05-07 10:35:50 mash: Waiting for createrepo to finish... 2009-05-07 10:35:50 mash: Running createrepo for out/centos4/x86_64/... Previous repo file missing: 2009-05-07 10:35:50 mash: Running createrepo for out/centos4/SRPMS... Previous repo file missing: 2009-05-07 10:35:50 mash: Waiting for depsolve and createrepo to finish... 2009-05-07 10:35:50 mash: Resolving multilib for arch x86_64 using method devel Traceback (most recent call last): File "/usr/bin/mash", line 82, in main() File "/usr/bin/mash", line 70, in main rc = themash.doMultilib() File "/usr/lib/python2.5/site-packages/mash/__init__.py", line 513, in doMultilib pid = self.doDepSolveAndMultilib(arch, repocache) File "/usr/lib/python2.5/site-packages/mash/__init__.py", line 464, in doDepSolveAndMultilib yumbase.doTsSetup() File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 86, in doTsSetup return self._getTs() File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 101, in _getTs self._getTsInfo(remove_only) File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 112, in _getTsInfo pkgSack = self.pkgSack File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 592, in pkgSack = property(fget=lambda self: self._getSacks(), File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 435, in _getSacks self.repos.populateSack(which=repos) File "/usr/lib/python2.5/site-packages/yum/repos.py", line 251, in populateSack sack.populate(repo, mdtype, callback, cacheonly) File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 162, in populate if self._check_db_version(repo, mydbtype): File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 223, in _check_db_version return repo._check_db_version(mdtype) File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 1147, in _check_db_version repoXML = self.repoXML File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 1305, in repoXML = property(fget=lambda self: self._getRepoXML(), File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 1301, in _getRepoXML raise Errors.RepoError, msg yum.Errors.RepoError: Cannot retrieve repository metadata (repomd.xml) for repository: centos4-x86_64. Please verify its path and try again 2009-05-07 10:35:51 mash: Depsolve and createrepo finished. mash failed in out/centos4 Any ideas? Steve -- Steve Traylen -- 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 ?
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
