md5 checksums are not updated ==> equery check {package containing .la files} fails for .la files. Reproducible: Always Steps to Reproduce: run lafilefixer if it updates f.e. linphone then 'equery check linphone' fails for md5 errors on .la files. Actual Results: $ equery check linphone [ Checking net-voip/linphone-3.0.0 ] /usr/lib/linphone/libmediastreamer.la has incorrect md5sum /usr/lib/linphone/liblinphone.la has incorrect md5sum * 105 out of 107 files good Expected Results: $ equery check linphone [ Checking net-voip/linphone-3.0.0 ] * 107 out of 107 files good
Not a bug. The files will still be unmerged with portage from within the last year. This is as-designed.
I beg to differ, This is not a bug about emerge --unmerge, It is about 'equery check' that cannot be trusted anymore. So it needs to be documented in my opinion in both lafilefixer that it will damage portage's md5 checksums for *.la files that need to be updated as well as in equery that false positives may arise from the use of lafilefixer. Or consider 'equery check' obsolete and remove it.
Your oppinion is that packet verification is NOT immportant. I tend to disagree. But there is a more serious issue. Appearantly .la files do not get removed when remerging kits that don't supply a new .la anymore After that a revdep-rebuild fails.!!! on a bunch of inconsistent .la file mess. see below: (I'll make abstract of the list) First like: * broken /usr/kde/3.5/lib/kde3/libksync_debugger.la (requires -lksync2) * broken /usr/kde/3.5/lib/kde3/libksync_pluckerpart.la (requires -lkitchensyncui) * broken /usr/kde/3.5/lib/kde3/libksync_pluckerpart.la (requires -lkonnector) * broken /usr/kde/3.5/lib/kde3/libksync_pluckerpart.la (requires -lksync2) * broken /usr/kde/3.5/lib/kde3/libksync_restore.la (requires -lkitchensyncui) * broken /usr/kde/3.5/lib/kde3/libksync_restore.la (requires -lkonnector) * broken /usr/kde/3.5/lib/kde3/libksync_restore.la (requires -lksync2) * broken /usr/kde/3.5/lib/kde3/libksync_syncerpart.la (requires -lkitchensyncui) * broken /usr/kde/3.5/lib/kde3/libksync_syncerpart.la (requires -lkonnector) * broken /usr/kde/3.5/lib/kde3/libksync_syncerpart.la (requires -lksync2) * broken /usr/kde/3.5/lib/kde3/libksync_viewer.la (requires -lkitchensyncui) * broken /usr/kde/3.5/lib/kde3/libksync_viewer.la (requires -lkonnector) * broken /usr/kde/3.5/lib/kde3/libksync_viewer.la (requires -lksync2) * broken /usr/kde/3.5/lib/kde3/libmultisynkpart.la (requires -lmultisynk) And later on: * !!! /usr/kde/3.5/lib/kde3/libksync_viewer.la not owned by any package is broken !!! * /usr/kde/3.5/lib/kde3/libksync_viewer.la -> (none) * !!! /usr/kde/3.5/lib/kde3/libmultisynkpart.la not owned by any package is broken !!! * /usr/kde/3.5/lib/kde3/libmultisynkpart.la -> (none) * !!! /usr/kde/3.5/lib/kde3/liboverviewpart.la not owned by any package is broken !!! * /usr/kde/3.5/lib/kde3/liboverviewpart.la -> (none) * !!! /usr/kde/3.5/lib/libkabckonnector.la not owned by any package is broken !!! * /usr/kde/3.5/lib/libkabckonnector.la -> (none) * !!! /usr/kde/3.5/lib/libkcalkonnector.la not owned by any package is broken !!! * /usr/kde/3.5/lib/libkcalkonnector.la -> (none) * !!! /usr/kde/3.5/lib/libkitchensyncui.la not owned by any package is broken !!! * /usr/kde/3.5/lib/libkitchensyncui.la -> (none) * !!! /usr/kde/3.5/lib/libkonnector.la not owned by any package is broken !!! The .la files are left on disk. Het is an ls -l xxxx ~ # ls -l /usr/kde/3.5/lib/kde3/libksync* -rw-r--r-- 1 root root 1495 Jun 16 17:29 /usr/kde/3.5/lib/kde3/libksync_backup.la -rw-r--r-- 1 root root 1507 Jun 16 17:29 /usr/kde/3.5/lib/kde3/libksync_debugger.la -rw-r--r-- 1 root root 1525 Jun 16 17:29 /usr/kde/3.5/lib/kde3/libksync_pluckerpart.la -rw-r--r-- 1 root root 1501 Jun 16 17:29 /usr/kde/3.5/lib/kde3/libksync_restore.la -rw-r--r-- 1 root root 1519 Jun 16 17:29 /usr/kde/3.5/lib/kde3/libksync_syncerpart.la -rw-r--r-- 1 root root 1495 Jun 16 17:29 /usr/kde/3.5/lib/kde3/libksync_viewer.la so you should consider updating the md5sums etc.
(In reply to comment #3) > Your oppinion is that packet verification is NOT immportant. I tend to > disagree. But there is a more serious issue. Please open a new bug with your emerge --info attached. .la files should be unmerged if you have unmerge-orphans in FEATURES. That is the default. If you have changed it, you will have to deal with the fallout. If not, you discovered a bug in portage. The current bug (274585) is about MD5 sum verification. That cannot be fixed in any reasonable way, other than to not use lafilefixer. Please use revdep-rebuild instead if MD5 sum verification of .la files is important for you.
If you want correct md5sums you should consider adding something like this to your /etc/portage/bashrc: post_src_install() { echo "post_src_install: run lafilefixer ${D}" lafilefixer "${D}" echo "" } This way the libtool archives are fixed after the install phase and before merging into the system. So the md5sums of the corrected *.la files are stored and equery does not complain.
