Getting CentOS up to date on SPARC

On Thu, 2006-06-22 at 22:20 -0500, Anthony Brooks wrote:
> Karanbir Singh wrote:
> 
> > We are presently looking for a Sparc maintainer (
or two, would be
> > better ) - Pasi has way too much work on his plate
at the moment and is
> > also already doing ( and will continue to do so,
for the time being )
> > his other arch's ( ia64/ s390(x) / Alpha ). But
he has expressed desire
> > to resign the Sparc build.
> > 
> > If you are interested, and have the time to spend
this might be
> > something you can get involved with ?
> 
> I have a couple of SunBlade 100's sitting here at the
house. I would love to
> help out in CentOS Sparc development. 

I have a very nice donation coming from Sun wrt SPARC .. it
is a T2000
machine (quite an impressive machine actually ... 32GB RAM,
8 Core
1.2GHZ processor).  The server should be here by the middle
of next
week ... and I will be able to see if I can compile normal
SPARC
packages as well as new Niagara packages on it.

Sun has been very nice to CentOS ... I would like to thank
them once
again for an unbelievable hardware donation.

Thanks,
Johnny Hughes
_______________________________________________
CentOS-devel mailing list
CentOS-develcentos.org
http://lists.centos.org/mailman/listinfo/centos-devel

Johnny Hughes wrote:
> I have a very nice donation coming from Sun wrt SPARC
.. it is a T2000
> machine (quite an impressive machine actually ... 32GB
RAM, 8 Core
> 1.2GHZ processor).  The server should be here by the
middle of next
> week ... and I will be able to see if I can compile
normal SPARC
> packages as well as new Niagara packages on it.

We should try and get a proper buildsystem on there, so that
people can
request builds and get the built pkgs online somewhere (
dev.centos.org
would be a good choice, i think )

Since most of the guys have local machines to test + do
-devel stuff on,
a single buildbox of this nature would be great.

- KB

-- 
Karanbir Singh : http://www.karan.org/ :
2522219icq
_______________________________________________
CentOS-devel mailing list
CentOS-develcentos.org
http://lists.centos.org/mailman/listinfo/centos-devel

Karanbir Singh napsal(a):
> We should try and get a proper buildsystem on there, so
that people can
> request builds and get the built pkgs online somewhere
( dev.centos.org
> would be a good choice, i think )
> 
> Since most of the guys have local machines to test + do
-devel stuff on,
> a single buildbox of this nature would be great.
> 
> - KB
> 

Well, are we going to use Mock? Last few weeks I've been
playing with
Mock on Centos, and it works pretty fine.
David Hrbáč
_______________________________________________
CentOS-devel mailing list
CentOS-develcentos.org
http://lists.centos.org/mailman/listinfo/centos-devel

David Hrbáč wrote:
> Karanbir Singh napsal(a):
>> We should try and get a proper buildsystem on
there, so that people can
>> request builds and get the built pkgs online
somewhere ( dev.centos.org
>> would be a good choice, i think )
>>
>> Since most of the guys have local machines to test
+ do -devel stuff on,
>> a single buildbox of this nature would be great.
> 
> Well, are we going to use Mock? Last few weeks I've
been playing with
> Mock on Centos, and it works pretty fine.

no. We dont / cant use Mock or any such builder for the
distro. I am 
doing some docs + a sort of HOWTO for people to use the
system that we 
have in place. Will post it on the wiki and a URL here as
soon as its done.

-- 
Karanbir Singh : http://www.karan.org/ :
2522219icq
_______________________________________________
CentOS-devel mailing list
CentOS-develcentos.org
http://lists.centos.org/mailman/listinfo/centos-devel

On Mon, 2006-06-26 at 10:09 +0100, Karanbir Singh wrote:
> David Hrbáč wrote:
> > Karanbir Singh napsal(a):
> >> We should try and get a proper buildsystem on
there, so that people can
> >> request builds and get the built pkgs online
somewhere ( dev.centos.org
> >> would be a good choice, i think )
> >>
> >> Since most of the guys have local machines to
test + do -devel stuff on,
> >> a single buildbox of this nature would be
great.
> > 
> > Well, are we going to use Mock? Last few weeks
I've been playing with
> > Mock on Centos, and it works pretty fine.
> 
> no. We dont / cant use Mock or any such builder for the
distro. I am 
> doing some docs + a sort of HOWTO for people to use the
system that we 
> have in place. Will post it on the wiki and a URL here
as soon as its done.

Why can't mock be used?

-sv


_______________________________________________
CentOS-devel mailing list
CentOS-develcentos.org
http://lists.centos.org/mailman/listinfo/centos-devel

On Mon, 2006-06-26 at 07:28 -0400, seth vidal wrote:
> On Mon, 2006-06-26 at 10:09 +0100, Karanbir Singh
wrote:
> > David Hrbáč wrote:
> > > Karanbir Singh napsal(a):
> > >> We should try and get a proper
buildsystem on there, so that people can
> > >> request builds and get the built pkgs
online somewhere ( dev.centos.org
> > >> would be a good choice, i think )
> > >>
> > >> Since most of the guys have local
machines to test + do -devel stuff on,
> > >> a single buildbox of this nature would be
great.
> > > 
> > > Well, are we going to use Mock? Last few
weeks I've been playing with
> > > Mock on Centos, and it works pretty fine.
> > 
> > no. We dont / cant use Mock or any such builder
for the distro. I am 
> > doing some docs + a sort of HOWTO for people to
use the system that we 
> > have in place. Will post it on the wiki and a URL
here as soon as its done.
> 
> Why can't mock be used?
> 
> -sv
> 
> 

As you should well be aware 

There are many hidden build requirements in the FC3 / RHEL4
package set.
So, a technology like mock will not (at lease easily)
properly build all
packages for that group of packages.

The upstream team is working hard to address those issues
and it should
not be the case with newer distros.  They will (supposedly)
properly
call out all build requirements.

If all the packages properly called out all their
"build requires", then
using a system like mock would work (that is, using a system
that
creates a chroot containing a core set of packages and all
the "build
requires" of the package to be built).

Currently, the CentOS build team uses a predefined build
host to build
packages.  That build host is a controlled machine that has
the latest
version of the arch in question and no other packages.

Thanks,
Johnny Hughes
_______________________________________________
CentOS-devel mailing list
CentOS-develcentos.org
http://lists.centos.org/mailman/listinfo/centos-devel

On Jun 26, 2006, at 7:37 AM, Johnny Hughes wrote:

> On Mon, 2006-06-26 at 07:28 -0400, seth vidal wrote:
>> On Mon, 2006-06-26 at 10:09 +0100, Karanbir Singh
wrote:
>>> David Hrbáč wrote:
>>>> Karanbir Singh napsal(a):
>>>>> We should try and get a proper
buildsystem on there, so that  
>>>>> people can
>>>>> request builds and get the built pkgs
online somewhere  
>>>>> ( dev.centos.org
>>>>> would be a good choice, i think )
>>>>>
>>>>> Since most of the guys have local
machines to test + do -devel  
>>>>> stuff on,
>>>>> a single buildbox of this nature would
be great.
>>>>
>>>> Well, are we going to use Mock? Last few
weeks I've been playing  
>>>> with
>>>> Mock on Centos, and it works pretty fine.
>>>
>>> no. We dont / cant use Mock or any such builder
for the distro. I am
>>> doing some docs + a sort of HOWTO for people to
use the system  
>>> that we
>>> have in place. Will post it on the wiki and a
URL here as soon as  
>>> its done.
>>
>> Why can't mock be used?
>>
>> -sv
>>
>>
>
> As you should well be aware 
>
> There are many hidden build requirements in the FC3 /
RHEL4 package  
> set.
> So, a technology like mock will not (at lease easily)
properly  
> build all
> packages for that group of packages.
>

While there may be many missing build dependencies, the
issues of  
building
a package, updating the build system to the latest
available, and  
populating
a build root are different.

I'm quite sure that mock can help with 1) and 2), and
populating a  
build root
can be done by increasing the packages in the base system to
cover  
missing
dependencies.

> The upstream team is working hard to address those
issues and it  
> should
> not be the case with newer distros.  They will
(supposedly) properly
> call out all build requirements.
>
> If all the packages properly called out all their
"build requires",  
> then
> using a system like mock would work (that is, using a
system that
> creates a chroot containing a core set of packages and
all the "build
> requires" of the package to be built).
>
> Currently, the CentOS build team uses a predefined
build host to build
> packages.  That build host is a controlled machine that
has the latest
> version of the arch in question and no other packages.
>

Everything installed on a single arch build server works
too, and is  
easy to maintain.


73 de Jeff_______________________________________________
CentOS-devel mailing list
CentOS-develcentos.org
http://lists.centos.org/mailman/listinfo/centos-devel

Jeff Johnson napsal(a):
> 
> While there may be many missing build dependencies, the
issues of building
> a package, updating the build system to the latest
available, and
> populating
> a build root are different.
> 
> I'm quite sure that mock can help with 1) and 2), and
populating a build
> root
> can be done by increasing the packages in the base
system to cover missing
> dependencies.
> 
That's why I'm pointing to Mock. We are able to find
missing
dependencies, files, srpms, and etc with Mock easily. This
part of rpms
QA will be covered. We know, many srpms are not complete,
one to point
is iptables-devel.
David Hrbac


_______________________________________________
CentOS-devel mailing list
CentOS-develcentos.org
http://lists.centos.org/mailman/listinfo/centos-devel