I've a puzzle on koji when build x86_64 arch.
by Jian Lee
I'just verify the
http://kojipkgs.fedoraproject.org/packages/rsh/0.17/54.fc11/data/logs/x86...,
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.gnu(a)gmail.com
14 years, 10 months
mash fails for me with x86_64.
by Steve Traylen
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 <lambda>
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 <module>
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 <lambda>
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 <lambda>
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
14 years, 10 months
How to do when build x86_64 pkgs needed i386 pkgs, but i386 pkgs have some files contented in x86_64 pkgs ?
by Jian Lee
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
Repository Size
DEBUG util.py:256:
=============================================================================
DEBUG util.py:256: Installing:
DEBUG util.py:256: libtermcap-devel i386 2.0.8-46.1
build 51 k
DEBUG util.py:256: libtermcap-devel x86_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: cracklib i386 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: libsepol i386 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.gnu(a)gmail.com
14 years, 10 months
how init mock ? there are need some packages about i386 for build x86_64 packages !
by Jian Lee
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.gnu(a)gmail.com
14 years, 11 months
Make sources?
by Brian Kosick
Hi All,
So I think that I have successfully upgraded koji from 1.2.6 to 1.3.1 by
doing this. I just have a few issues to work out....
1) install the koji 1.3.1 rpms
2) update the db schema pgsql -h kojihost koji koji
< /usr/share/doc/koji-1.3.1/docs/schema-upgrade-1.2-1.3.sql
3) started kojid and kojira
When I did my first build, I got stuck with koji not having a mock group
srpm-build
I setup the mock group with
koji add-group dist-el5-build srpm-build
koji add-group-pkg dist-el5-build srpm-build pkg1 pkg2 pk3
I then added that group to my build dist with
koji call addGroupList dist-mxl-el5-build srpm-build
When I do a koji list-groups dist-mxl-el5-build i get
koji list-groups dist-mxl-el5-build
build [dist-mxl-el5-build]
<snip for brevity>
srpm-build [dist-el5-build]
automake: None, default [dist-el5-build]
bash: None, default [dist-el5-build]
buildsys-macros: None, default [dist-el5-build]
bzip2: None, default [dist-el5-build]
bzip2-devel: None, default [dist-el5-build]
coreutils: None, default [dist-el5-build]
cpio: None, default [dist-el5-build]
diffutils: None, default [dist-el5-build]
elfutils: None, default [dist-el5-build]
elfutils-libelf: None, default [dist-el5-build]
file: None, default [dist-el5-build]
gcc: None, default [dist-el5-build]
gcc-c++: None, default [dist-el5-build]
glibc: None, default [dist-el5-build]
glibc-common: None, default [dist-el5-build]
glibc-devel: None, default [dist-el5-build]
glibc-headers: None, default [dist-el5-build]
gzip: None, default [dist-el5-build]
info: None, default [dist-el5-build]
libselinux: None, default [dist-el5-build]
libsemanage: None, default [dist-el5-build]
libsepol: None, default [dist-el5-build]
libtool-ltdl: None, default [dist-el5-build]
make: None, default [dist-el5-build]
patch: None, default [dist-el5-build]
perl: None, default [dist-el5-build]
policycoreutils: None, default [dist-el5-build]
python: None, default [dist-el5-build]
readline: None, default [dist-el5-build]
readline-devel: None, default [dist-el5-build]
redhat-release: None, default [dist-el5-build]
redhat-rpm-config: None, default [dist-el5-build]
rpm-build: None, default [dist-el5-build]
rpm-libs: None, default [dist-el5-build]
sed: None, default [dist-el5-build]
selinux-policy: None, default [dist-el5-build]
shadow-utils: None, default [dist-el5-build]
sqlite: None, default [dist-el5-build]
tar: None, default [dist-el5-build]
unzip: None, default [dist-el5-build]
which: None, default [dist-el5-build]
zip: None, default [dist-el5-build]
zlib-devel: None, default [dist-el5-build]
It appears that the repos have regenned and now when I try to do a
build, I'm getting
DEBUG util.py:280: Executing command: ['make', 'sources']
DEBUG util.py:256: make: *** No rule to make target `sources'. Stop.
DEBUG util.py:319: Child returncode was: 2
Has a new make command "sources" been created similar to "make srpm"?
If so what does it do and what does koji expect back?
Brian
14 years, 11 months
Koji End User support
by Brian Kosick
Hi All,
I have koji running great on a single server setup, and have gotten to
go ahead to start rolling it out/letting our dev's play with it. I
have a question, commands like "koji build dist-el5 SCMURL?pkgname#tip"
work fine on the koji server, but when I install the koji rpm say on my
laptop, I keep getting errors like:
koji build dist-el5 SCMURL?pkg#tip
Unable to log in, no authentication methods available
My user certs have not changed, and my $HOME is NFS roaming so it's the
same on the Koji Server and on the "dev" laptop, and the user SSL Certs
are in the same location.
I do not want to set this up to be a "builder" box that actually does
the builds, I want to install on a DEV laptop and have them be able to
call a koji build from there, rather than having to login to the koji
server.
I took a look at the Howto's and this sort of config/setup doesn't seem
to be addressed or I just may be dense and missed it. I would
appreciate it if someone could point me in the right direction for this
sort of setup.
Brian
14 years, 11 months