https://bugzilla.novell.com/show_bug.cgi?id=227670 greg.riedesel@wwu.edu changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|greg.riedesel@wwu.edu | ------- Comment #10 from greg.riedesel@wwu.edu 2007-01-24 09:30 MST ------- The environment I witnessed the bug is long gone, both on the NFS-server side and on the server I was attempting to install. During the install process it downloads packages and installs them. When I had it pointed at an OES SP2 server (patches up to date as of 12/1/06 at the time of this report), it would continue until a random point and complain that a package had failed validation. I flip to the console and drill down the file-system to get to the NFS-mounted area. Running md5sum on the package (sha1sum apparently isn't in the stripped down install environment) yielded a md5sum that was different from when I run md5sum directly on the OES SP2 server itself. Manually unmounting and remounting the NFS source to the same mount-point, seemed to reset that behavior. Running md5sum on the install server, still in the install shell, gives a different md5sum than it did before the umount/mount; a correct one. I then continue installation. It never complained on the same package twice, and I attempted to install openSUSE many times before I figured out the umount/mount trick. The NFS server was presenting a directory tree that was an iso-image mounted locally, the iso-image itself passed its sha1sum. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.