Folks, I'm running into the funness that documented here: https://bugzilla.redhat.com/show_bug.cgi?id=433579 and discussed on the CentOS list: http://lists.centos.org/pipermail/centos/2009-April/074912.html In building a chroot, pam is installed before coreutils causing its %post script to fail, yum to report an error code to mock, and mock refusing to continue with the build. In fact, my case exactly matches the CentOS thread just in RHEL 5.3. I hesitate to patch and push a custom pam package because of a backwards dependency loop. Would anyone know how to jiggle yum or mock just enough to ignore or get the loop in the right order for my build machines? This is yum 3.2.19. Jack Neely -- Jack Neely <jjneely@xxxxxxxx> Linux Czar, OIT Campus Linux Services Office of Information Technology, NC State University GPG Fingerprint: 1917 5AC1 E828 9337 7AA4 EA6B 213B 765F 3B6A 5B89 _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxx http://lists.baseurl.org/mailman/listinfo/yum