I recently experienced with SuSE 9.2 the suse build script used by suse to build packages in a chrooted environment (See http://www.novell.com/coolsolutions/feature/11793.html for more informations about the build script). Since 9.3 (build-2005.3.11-3-noarch.rpm), some problems appeared. First problem: build do not seem know any of the suse metapackage anymore (metapackage name are given in the suse package convention http://ftp.novell.com/pub/forge/library/SUSE%20Package%20Conventions/spc.htm...). When calling a suse metapackage (such as gnome2-devel-packages or x-devel-package) in the #needeforbuild tag, the build script tells it doesn't know such meta package. Thus in order to compile a gkt2 app, I need to manually add all the gtk2 and gnome devel packages in the #needeforbuild tag, which is really annoing. Second problem: After a successfull compilation with build, if I want to start an other compilation, build always faill with the following error: error: failed to stat /lib/klibc/dev: no such file or directory package filesystem-9.3-2 is already installed In order to continu the compilation process, the build script must rebuilt the complete chrooted environment each time I use it, which is also annoing. So here are my questions: - Is there a more recent rpm of the build script available anywhere ??? - I didn't experiment those kind of "bug" with SuSE 9.2, thus, is there something wrong with the build script provided with 9.3 or is there something i'm doing wrong now ??