I don't know if this is a recent change, but I'm seeing yum exit non-0 when installation of packages went fine, but some scriptlets failed. This is most notable when doing an anaconda compose and anaconda installs 400+ packages in a chroot and uses the nodocs flag. Tons of things fail their install-info %post commands. Unfortunately the anaconda script sees that yum exited non-0 and assumes that nothing got installed, and bails on the rest of the compose. Anybody know what's going on here? Did yum change recently? It doesn't look like it by running the most recent previous f11 build of yum, so maybe it's done this for a while, and some new breakage in our packages is leading to this.
In what scenarios will yum "successfully" install packages, but exit with non-0? Complete! mock-chroot> echo $? 1 -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Yum-devel mailing list Yum-devel@lists.baseurl.org http://lists.baseurl.org/mailman/listinfo/yum-devel
