chroots are not getting cleaned up because rmake user can not remove the root directory.
gcc/root is getting made dr-xr-xr-x 2 rmake rmake 60 2014-02-13 18:21 root and it is keeping rmake from removing the chroot the file tagscripts is in the directory but the perms are right on it. My guess is our own tagscripts are causing this problem. I am looking into that now -- Brett C. Smith [email protected] Sr Software Developer Platform Deployment Technologies (919)531-6635 -- x16635 ________________________________________ From: Foresight-devel <[email protected]> on behalf of Michael K. Johnson <[email protected]> Sent: Saturday, February 22, 2014 3:49 PM To: Foresight Linux Development Subject: [Foresight-devel] Re: rmake chroots fixed On Sat, Feb 22, 2014 at 03:38:57PM -0500, Michael K. Johnson wrote: > The kernel package, which is seeing builds as duplicate, has > failed in the same manner. There, I think the duplicate flavors > are mirrorball configuration problems where the mirrorball > configuration for kernel flavors doesn't yet match the set > of kernels Fedora ships. The flavors look right, but I don't see anything in the factory to split out the kernels by matching flavors to the package names. Maybe that got lost in simplification. That may or may not be related to rmake getting confused about chroots. I think it shows up when builds are entirely sequential between packages built in a single job, so that rmake is trying to reuse a chroot name, but the chroot didn't get cleaned up right. I'm finding that the chroots are not being cleaned up now and I don't know why. Seems like a bug in the chroot helper, but it isn't logging errors. _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
