The first time up2date is run it seems to modify a lot of .pyc files. After that rpm -V updates prints: SM5....T /usr/share/rhn/up2date_client/bootloadercfg.pyc SM5....T /usr/share/rhn/up2date_client/checkbootloader.pyc SM5....T /usr/share/rhn/up2date_client/config.pyc SM5....T /usr/share/rhn/up2date_client/depSolver.pyc SM5....T /usr/share/rhn/up2date_client/gpgUtils.pyc SM5....T /usr/share/rhn/up2date_client/hardware.pyc SM5....T /usr/share/rhn/up2date_client/headers.pyc SM5....T /usr/share/rhn/up2date_client/iutil.pyc SM5....T /usr/share/rhn/up2date_client/lilo.pyc SM5....T /usr/share/rhn/up2date_client/lilocfg.pyc SM5....T /usr/share/rhn/up2date_client/packageList.pyc SM5....T /usr/share/rhn/up2date_client/rhnChannel.pyc SM5....T /usr/share/rhn/up2date_client/rhnDefines.pyc SM5....T /usr/share/rhn/up2date_client/rhnErrata.pyc SM5....T /usr/share/rhn/up2date_client/rhnHTTPlib.pyc SM5....T /usr/share/rhn/up2date_client/rhnHardware.pyc SM5....T /usr/share/rhn/up2date_client/rhnPackageInfo.pyc SM5....T /usr/share/rhn/up2date_client/rpcServer.pyc SM5....T /usr/share/rhn/up2date_client/rpmSource.pyc SM5....T /usr/share/rhn/up2date_client/rpmUtils.pyc SM5....T /usr/share/rhn/up2date_client/translate.pyc SM5....T /usr/share/rhn/up2date_client/up2date.pyc SM5....T /usr/share/rhn/up2date_client/up2dateAuth.pyc SM5....T /usr/share/rhn/up2date_client/up2dateBatch.pyc SM5....T /usr/share/rhn/up2date_client/up2dateErrors.pyc SM5....T /usr/share/rhn/up2date_client/up2dateLog.pyc SM5....T /usr/share/rhn/up2date_client/up2dateMessages.pyc SM5....T /usr/share/rhn/up2date_client/up2dateUtils.pyc SM5....T /usr/share/rhn/up2date_client/wrapperUtils.pyc Should this really be happening? % rpm -q python rhnlib up2date up2date-gnome python-2.2.1-10 rhnlib-0.8-2 up2date-2.9.13-7.x.9 up2date-gnome-2.9.13-7.x.9
I"m not exactly sure why it does that... investigating...
As best I can tell, this is normal behaviour. The *.pyc files are being recompiled when the app runs. Deffering for now, will take a look at it for the next release.
Still there in Phoebe.
Still there is Rawhide (up2date-3.0.40-1).
3.1.x seems to have finally fixed this. Closing.
Sorry, still there. With Severn + up2date-3.9.20-2, I still get: SM5....T /usr/share/rhn/up2date_client/repoBackends/__init__.pyc SM5....T /usr/share/rhn/up2date_client/repoBackends/aptRepo.pyc SM5....T /usr/share/rhn/up2date_client/repoBackends/dirRepo.pyc SM5....T /usr/share/rhn/up2date_client/repoBackends/genericRepo.pyc SM5....T /usr/share/rhn/up2date_client/repoBackends/genericSolveDep.pyc SM5....T /usr/share/rhn/up2date_client/repoBackends/up2dateRepo.pyc SM5....T /usr/share/rhn/up2date_client/repoBackends/urlUtils.pyc SM5....T /usr/share/rhn/up2date_client/repoBackends/yumRepo.pyc SM5....T /usr/share/rhn/up2date_client/up2dateUtils.pyc
With up2date-3.9.28-2, I still get: SM5....T /usr/share/rhn/actions/__init__.pyc SM5....T /usr/share/rhn/actions/packages.pyc SM5....T /usr/share/rhn/up2date_client/repoBackends/__init__.pyc SM5....T /usr/share/rhn/up2date_client/repoBackends/aptRepo.pyc SM5....T /usr/share/rhn/up2date_client/repoBackends/dirRepo.pyc SM5....T /usr/share/rhn/up2date_client/repoBackends/genericRepo.pyc SM5....T /usr/share/rhn/up2date_client/repoBackends/genericSolveDep.pyc SM5....T /usr/share/rhn/up2date_client/repoBackends/up2dateRepo.pyc SM5....T /usr/share/rhn/up2date_client/repoBackends/urlUtils.pyc SM5....T /usr/share/rhn/up2date_client/repoBackends/yumRepo.pyc SM5....T /usr/share/rhn/up2date_client/up2dateUtils.pyc
Still there with up2date-4.3.8-1
I just checked in a fix for mailman that works for that similar problem. msw said that recipe should work for any python package. I would attempt to modify up2date right now, but I can't find it in the CVS.
this bug seems to be fixed in Fedora Core 2 up2date-4.3.19-1
Yes, indeed. Changelog shows: * Thu May 06 2004 Warren Togami <wtogami> - #69205 bytecompile for rpm -V Thanks, Warren!