FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor


 
 
LinkBack Thread Tools
 
Old 11-24-2010, 02:59 PM
Jinze Xue
 
Default for help

I want to move*all data from a* old koji build system to a new os, what's the best way to do?
*
*
*
and who have documents about configs and steps to build cvs system for a koji build system ? send me ,thanks very much*** !!!!!!!
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 12-03-2010, 01:14 PM
Jinze Xue
 
Default for help

hellowhen I build rpms from cvs SCM ,builds failed with error these:



DEBUG backend.py:682: */usr/bin/yum --installroot /var/lib/mock/dist-ky3.2-build-63-18/root/ *groupinstall srpm-build
DEBUG util.py:301: *Executing command: /usr/bin/yum --installroot /var/lib/mock/dist-ky3.2-build-63-18/root/ *groupinstall srpm-buildDEBUG util.py:267: *file:///mnt/koji/repos/dist-ky3.2-build/18/i386/repodata/repomd.xml: [Errno 14] Could not open/read file:///mnt/koji/repos/dist-ky3.2-build/18/i386/repodata/repomd.xml
DEBUG util.py:267: *Trying other mirror.DEBUG util.py:267: *Error: Cannot retrieve repository metadata (repomd.xml) for repository: build. Please verify its path and try again


with the the one server and the one client, the error sometimes like this:

$ cvs -d : pserver:anonynous@172.19.0.30:/cvs checkout -r avalon-logkit-1_2.......
Fatal error, aborting.anonymous: no such user

my config of cvs client is right ,is there something wrong with my cvs server?*

any help is good ,thanks everyone , waiting...............
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 12-03-2010, 07:45 PM
Mike McLean
 
Default for help

On 11/24/2010 10:59 AM, Jinze Xue wrote:
> I want to move all data from a old koji build system to a new os, what's
> the best way to do?

A koji system generally includes multiple hosts, so I'm not sure which
ones you are need to migrate. I'm also not sure what os you're moving
from and to, or how.

For build hosts, it's generally just a matter of preserving the files
under /etc/koji: mainly kojid.conf, but possibly also some key files for
authentication. Once the new OS is installed/upgraded, make sure
koji-builder is installed and that the config files are intact.

For host(s) running koji-hub and/or koji-web it is much the same.
Preserve the necessary config files, and restart the services after the
migration.

For your postgresql server, well, you should probably refer to the
postgresql manual for completeness. Short version... you'll want to back
up your koji database with pg_dump before you do anything. If the
version of postgres in the new os is not too different, you can probably
manage with just preserving all the /var/lib/pgsql/ content. If not, you
can restore from your dump with pg_restore. You'll also need to preserve
key postgres config settings, particularly those that allow koji-hub to
access the database.

> and who have documents about configs and steps to build cvs system for a
> koji build system ? send me ,thanks very much !!!!!!!

Most of the complication here comes from koji's support of the somewhat
messy dist-cvs system that Fedora used to use. However, you don't have
to use such a complicated setup. You can skip all the common dir stuff
if you make sure all the cvs modules you build handle the following sanely:
1) issuing 'make sources' in the checkout dir does something sane (or
at least is an error-free no-op)[*]
2) the checkout contains exactly one spec file
3) the checkout contains all the necessary files for rpmbuild to build
the srpm from that spec file
[*] in the allowed_scms config for your build hosts, you can change the
'make sources' command to something else for individual scms.

I should point out that all of this is true for git and svn as well.
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 12-17-2010, 05:44 AM
Jinze Xue
 
Default for help

hello!I'm building some rpms of x86_64,and some of them need glibc-devel of i686 to build. but I can't add it into buildrequires. so it failed with error:*No Package Found For /usr/include/gnu/stubs-32.h
How could I solve this problem.Waiting for help,thanks all!!!
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 12-17-2010, 05:58 AM
Christos Triantafyllidis
 
Default for help

Hi Jinze,
i had the same issue with a nasty package and a solve it by altering the "mergerepo" script to add both x86_64 and i386 (and its relatives i586, i686 etc) in x86_64 repos. This worked fine for more than a year but broken my koji installation a few days ago where mock couldn't solve the dependancies for "curl" which required openssl. Reverting my change in mergerepo resolved the dependancies issues of curl. I'm still confused on what caused this issue but i think it has to do with the very recent update of openssl.

Regards,
Christos


On Dec 17, 2010, at 8:44 AM, Jinze Xue wrote:

> hello!
> I'm building some rpms of x86_64,and some of them need glibc-devel of i686 to build. but I can't add it into buildrequires. so it failed with error:
> No Package Found For /usr/include/gnu/stubs-32.h
> How could I solve this problem.Waiting for help,thanks all!!!
> --
> buildsys mailing list
> buildsys@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/buildsys

--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 12-17-2010, 04:08 PM
Mike McLean
 
Default for help

On 12/17/2010 01:44 AM, Jinze Xue wrote:
> hello!
> I'm building some rpms of x86_64,and some of them need glibc-devel of i686
> to build. but I can't add it into buildrequires. so it failed with error:
> No Package Found For /usr/include/gnu/stubs-32.h
> How could I solve this problem.Waiting for help,thanks all!!!

koji does not handle multilib repos, so it will not place i686 rpms in
an x86_64 repo. Very few builds require any sort of multilib content. I
tend to question the validity of such requirements.

The normal workaround for your issue is to build a 64bit rpm with the
necessary 32bit content. In Fedora, that package is glibc32.
http://koji.fedoraproject.org/koji/packageinfo?packageID=1160
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 

Thread Tools




All times are GMT. The time now is 01:35 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org