On Friday 22 September 2006 13:01, Steve Dickson wrote: > Yes... adding a build requirement did indeed fix the problem, but > thats not point... The point is by not installing some of the most > used package configuration tools (i.e. autoconf and automake), > the build process has a huge whole in which silent failures > of configuration patches can cause *undetectable* corrupted rpms > that will land on our user's systems. it is fairly well documented in the wiki the changes in the new build root and it has been tested alot. the guidelines are pretty clear on what is and is not included by default. If you call autoconf or outomake then you need to BR them its fairly simple. The problem should have shown up in your local mock build before you committed the build. Dennis -- Fedora-maintainers mailing list Fedora-maintainers@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers -- Fedora-maintainers-readonly mailing list Fedora-maintainers-readonly@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly
