"There's a hole in the bucket, Dear Liza, Dear Liza, ..."
I'm trying to build all the SRPMS from
http://www.linux911.cl/GFS-CENTOS4/, and have found a real dependency
mess, including some circular dependencies.
Has anyone found a clean way to bootstrap this collection of packages?
bash-3.00$ sudo rpm -Uhv /tmp/cman-1.0.1-0.i386.rpm /tmp/ccs-
ccs-1.0.1-20050705200822.i386.rpm
ccs-devel-1.0.1-20050705200822.i386.rpm
bash-3.00$ sudo rpm -Uhv /tmp/cman-1.0.1-0.i386.rpm
/tmp/ccs-1.0.1-20050705200822.i386.rpm
error: Failed dependencies:
magma-plugins is needed by ccs-1.0.1-20050705200822.i386
bash-3.00$ rpmbuild --rebuild magma-plugins-1.0.1-0.src.rpm
Installing magma-plugins-1.0.1-0.src.rpm
error: Failed build dependencies:
gulm-devel is needed by magma-plugins-1.0.1-0.i386
dlm-devel is needed by magma-plugins-1.0.1-0.i386
bash-3.00$ sudo rpm -Uhv /tmp/dlm-devel-1.4.0.8-20050705200822.i386.rpm
error: Failed dependencies:
dlm = 1.4.0.8-20050705200822 is needed by
dlm-devel-1.4.0.8-20050705200822.i386
bash-3.00$ sudo rpm -Uhv /tmp/dlm-devel-1.4.0.8-20050705200822.i386.rpm
/tmp/dlm-1.4.0.8-20050705200822.i386.rpm
error: Failed dependencies:
cman is needed by dlm-1.4.0.8-20050705200822.i386
bash-3.00$ sudo rpm -Uhv /tmp/dlm-devel-1.4.0.8-20050705200822.i386.rpm
/tmp/dlm-1.4.0.8-20050705200822.i386.rpm /tmp/cman-1.0.1-0.i386.rpm
error: Failed dependencies:
ccs is needed by cman-1.0.1-0.i386
bash-3.00$ sudo rpm -Uhv /tmp/dlm-devel-1.4.0.8-20050705200822.i386.rpm
/tmp/dlm-1.4.0.8-20050705200822.i386.rpm /tmp/cman-1.0.1-0.i386.rpm
/tmp/ccs-1.0.1-20050705200822.i386.rpm
error: Failed dependencies:
magma-plugins is needed by ccs-1.0.1-20050705200822.i386
bash-3.00$ rpmbuild --rebuild magma-plugins-1.0.1-0.src.rpm
Installing magma-plugins-1.0.1-0.src.rpm
error: Failed build dependencies:
gulm-devel is needed by magma-plugins-1.0.1-0.i386
dlm-devel is needed by magma-plugins-1.0.1-0.i386
bash-3.00$
As there seems to be a desire for official CentOS CS & GFS packages, we
should decide how these are going to be stored on the mirror.
The simple method is probably directories under {3,4} called {CS,GFS}.
(ie. new directories alongside extras, centosplus etc).
Can these directories easily be shared out to developers? I probably
need a new key to sign my packages, unless someone with the 3 key wants
to resign them after I sign then with the 2 key.
Given the low volume of updates in these trees, it might be easier if
someone with 3 access wants to manually take my packages and put them
into the 3 tree.
Also, how does stuff get into the vault? Is this automatic.
--
John Newbigin
Computer Systems Officer
Faculty of Information and Communication Technologies
Swinburne University of Technology
Melbourne, Australia
http://www.ict.swin.edu.au/staff/jnewbigin