Note that .pyc files are not included in the packaging, they are produced at install time, so they don't contribute to any checksums. The .py files do, but these aren't what trigger the error message.
The reason for this is that at package build time, you don't know what versions of Python may be installed on the target system, and .pyc files are Python version specific. IOW, a .pyc file built for Python 3.2 is not guaranteed to work for 3.3. AFAICT, what must have happened is that when a package was installed, and its pyc file was being written, *something* caused the pyc file to be truncated. The question is what though? Re-installing fixes the problem because the .pyc files are re-built at that time. Thus the corruption went away. If it's not a file system problem or a hardware problem, I'm not sure what it could be. Another thing to note is that Python does its best to write a new .pyc file atomically, so I can't see how this could be a race condition (e.g. one process trying to read a .pyc file while the installation process is writing it). Plus, if the write fails you won't get a bogus .pyc file *and* you'd get an exception. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058884 Title: do-release-upgrade crashed with EOFError in /usr/lib/ubuntu-release- upgrader/check-new-release: EOF read where not expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1058884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
