I did some investigations of Gareth and Erich Focht's error reports. Erich's error report was easily solved by adding more verbose error reporting to DepMan.pm -- previously, it just reported a terse "it didn't work" message, now it lists the missing packages and stops. This only affects RPMs when they are needed. The setup processing code, which had the opportunity to notice the missing RPM, remained blissfully ignorant and quiet...
Gareth's error, an rpm missing from /tftpboot/rpm while the image is being built, triggers an odd set of errors. When I removed the c3-ckillnode RPM from /tftpboot/rpm, update-rpms reported the error, but the image-building code continued on, with odd errors involving missing dependencies eventually being reported by rpm(1). While I didn't yet find out what causes those odd rpm(1) errors, the problem from update-rpms is now reported, and the process stops before the error can be generated. Both fixes are in the trunk (r3023), having undergone positive and negative unit tests. -- David N. Lombard My comments represent my opinions, not those of Intel Corporation. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
