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

Go Back   Linux Archive > CentOS > CentOS Development

 
 
LinkBack Thread Tools
 
Old 10-28-2009, 05:18 PM
Karanbir Singh
 
Default Mock patch speeds up 'mock init' to 5 Seconds from cache (linked, rsync'd)

On 10/28/2009 05:26 PM, Farkas Levente wrote:
> imho the buildserver should have to be very minimal basic setup

that is just noise. I'd really like to hear you argue package policy on
the hosted buildserver that does chrooted builds for the same arch it
runs as native.

in some corner cases, one might find socket overlap issues, but I'm
unaware of anything like that on the centos tree.

- KB
_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
http://lists.centos.org/mailman/listinfo/centos-devel
 
Old 10-28-2009, 06:36 PM
Jeff Johnson
 
Default Mock patch speeds up 'mock init' to 5 Seconds from cache (linked, rsync'd)

On Oct 28, 2009, at 1:34 PM, Shad L. Lords wrote:

> Brian Schueler wrote:
>> Therefore is the second copy named 'clean-cache-copy', which
>> repairs the tainted files. The clean-cache-copy is _not_ linked
>> and represent the original root cache. rsync syncs it to the
>> 'linked-cache-copy' and ensures that the content is always the
>> same before each mock build.
>
> And do all mock builds link against this copy? What happens if you
> have
> 3-4 builds going on at the same time? Are there any files that
> would be
> linked between chroots? (If all the chroots link to linked-cache-copy
> then the answer would be yes)
>

If 3-4 builds are going on simultaneously, then the issue
is "minimal suffcient" install to support all 3-4 builds,
not anything to do with hard links.

I would claim (but will not argue) that any build
that is affected by having more than the "minimal sufficient"
set of packages installed is broken for other reasons.

> If you are just making a copy for each chroot then that isn't really
> any
> different then just modifying existing behavior but removing the
> gzip on
> the tarball
>

Yes. Exactly. Hard links are just less costly than gunzip on a tarball.

And any package that changes a hard-linked file (your other msg) is
broken for
reasons that have nothing to do with whether hard links were used
to populate a build system. Use chattr(8) after doing the hard links
if you are worried about contamination. But some build, not the hard
linking,
is what was broken if pollution occurs. But yes, contamination of a
stateful
store also needs to be worried about.

hth

73 de Jeff
_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
http://lists.centos.org/mailman/listinfo/centos-devel
 
Old 10-28-2009, 07:49 PM
David Hrbáč
 
Default Mock patch speeds up 'mock init' to 5 Seconds from cache (linked, rsync'd)

Farkas Levente napsal(a):
> this is not true. we use mock 0.9 for all of our rebuild and mock 0.9
> work perfectly for us what's more it's faster the 0.6.
>

Right, it's much faster...
David Hrbáč
_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
http://lists.centos.org/mailman/listinfo/centos-devel
 
Old 10-28-2009, 07:53 PM
Seth Vidal
 
Default Mock patch speeds up 'mock init' to 5 Seconds from cache (linked, rsync'd)

On Wed, 28 Oct 2009, David Hrbáč wrote:


Farkas Levente napsal(a):

this is not true. we use mock 0.9 for all of our rebuild and mock 0.9
work perfectly for us what's more it's faster the 0.6.



Right, it's much faster...



I've been following this discussion for a while. If there are items you
want to get into upstream mock you should post them to the list where
mock's upstream is:


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

this list covers mock and koji.

-sv
_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
http://lists.centos.org/mailman/listinfo/centos-devel
 
Old 10-28-2009, 07:53 PM
David Hrbáč
 
Default Mock patch speeds up 'mock init' to 5 Seconds from cache (linked, rsync'd)

Farkas Levente napsal(a):
> imho the buildserver should have to be very minimal basic setup and in
> this case updating the buildserver to the latest centos version is
> recommended. but if you still like to run c3 on it you can still run
> 0.9 on c5 servers and the resulted rpms should have to be identical.

I do so with our building production. I have migrated everything to C5.x
with mock 0.9. I see no point in running C3 as build host. We are also
running all build hosts as vmware virtuals and C5 behaves better on VI
than C3.
David Hrbáč
_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
http://lists.centos.org/mailman/listinfo/centos-devel
 

Thread Tools




All times are GMT. The time now is 04:34 PM.

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