-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 BJ Dierkes wrote: >> >>> 1) more reliable mount/umount >>> several people have pointed out instances where mock exits leaving >>> mounts behind (specifically /dev), and the next invokation of mock >>> ends up 'rm -rf' the host machine's /dev. Bad.... >> >> And /dev/pts and /proc. >> > > Yes... this is one should be pushed way up in priority if possible... > building any apps around mock will lead to many a developer wondering > what just happened to their '/dev'... as is the case right now for > me.... atleast 10 times in the last few hours. > > Thanks.
I'm looking at BZ 250985 now. I'd like to add code to do two things: 1. Find where we're exiting without umounting 2. Add some paranoia code in the startup logic to not screw up if #1 fails (like is happening now). To that end, would you run one of your failure cases with mock --debug and send me the output? Thanks, Clark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHBRApHyuj/+TTEp0RAqW5AJ9M0tEIi7wMRSxMPTOvGvLr4nwr0ACbB3Qm bdfOov8fGh0optB3JdQ3hwA= =FiXR -----END PGP SIGNATURE----- -- Fedora-buildsys-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
