Hide Forgot
$ emacs -batch -f list-load-path-shadows Loading /usr/share/emacs/site-lisp/site-start.d/focus-init.el (source)... Loading /usr/share/emacs/site-lisp/site-start.d/php-mode-init.el (source)... Loading /usr/share/emacs/site-lisp/site-start.d/rpm-spec-mode-init.el (source)... This site has duplicate Lisp libraries with the same name. If a locally-installed Lisp library overrides a library in the Emacs release, that can cause trouble, and you should probably remove the locally-installed version unless you know what you are doing. /usr/share/emacs/site-lisp/flim/sha1 hides /usr/share/emacs/23.2/lisp/sha1 /usr/share/emacs/site-lisp/flim/md4 hides /usr/share/emacs/23.2/lisp/md4 /usr/share/emacs/site-lisp/flim/hex-util hides /usr/share/emacs/23.2/lisp/hex-util /usr/share/emacs/site-lisp/flim/hmac-def hides /usr/share/emacs/23.2/lisp/net/hmac-def /usr/share/emacs/site-lisp/flim/sasl hides /usr/share/emacs/23.2/lisp/net/sasl /usr/share/emacs/site-lisp/flim/sasl-ntlm hides /usr/share/emacs/23.2/lisp/net/sasl-ntlm /usr/share/emacs/site-lisp/flim/ntlm hides /usr/share/emacs/23.2/lisp/net/ntlm /usr/share/emacs/site-lisp/flim/sasl-digest hides /usr/share/emacs/23.2/lisp/net/sasl-digest /usr/share/emacs/site-lisp/flim/sasl-cram hides /usr/share/emacs/23.2/lisp/net/sasl-cram /usr/share/emacs/site-lisp/flim/hmac-md5 hides /usr/share/emacs/23.2/lisp/net/hmac-md5 10 Emacs Lisp load-path shadowings were found
Thanks for the report. Yes I noticed these shadows long ago too but didn't really know what to do for them. Can I ask what you use flim for? The only package that seems to use it now in Fedora is emacs-w3m. I tried running emacs-w3m without the above files (I don't think it actually uses any of those libraries) and basic browsing seems to work fine. AFAICS w3m-el only needs flim for mime support (I guess for rendering and editting html email, etc). Perhaps the files in question could be subpackaged or even removed.
I don't have any good idea how to fix this or time to do the testing needed before removing the files. I think we will just have to live with this duplication or not install flim...
Just remove them.
They are not identical files AFAICR. How do you use flim?
I don't want to be forced to use obsolete versions of these files.
(I don't think I was clear: the point is I believe the files are not obsolete but long forked or diverged, and they don't look compatible with the shadowed files IIRC.) Anyway I am going to try to remove the said files from f17 and let's see if anything actually breaks... Here are the results again for current F17: /usr/share/emacs/site-lisp/flim/md4 hides /usr/share/emacs/24.0.92/lisp/md4 /usr/share/emacs/site-lisp/flim/hex-util hides /usr/share/emacs/24.0.92/lisp/hex-util /usr/share/emacs/site-lisp/flim/sasl-cram hides /usr/share/emacs/24.0.92/lisp/net/sasl-cram /usr/share/emacs/site-lisp/flim/sasl-digest hides /usr/share/emacs/24.0.92/lisp/net/sasl-digest /usr/share/emacs/site-lisp/flim/ntlm hides /usr/share/emacs/24.0.92/lisp/net/ntlm /usr/share/emacs/site-lisp/flim/sasl hides /usr/share/emacs/24.0.92/lisp/net/sasl /usr/share/emacs/site-lisp/flim/sasl-ntlm hides /usr/share/emacs/24.0.92/lisp/net/sasl-ntlm /usr/share/emacs/site-lisp/flim/hmac-def hides /usr/share/emacs/24.0.92/lisp/net/hmac-def /usr/share/emacs/site-lisp/flim/hmac-md5 hides /usr/share/emacs/24.0.92/lisp/net/hmac-md5 (Perhaps it would actually be better if site-lisp/flim was behind 24.0.92/lisp/* in load-path.) Anyway should be "fixed" in flim-1.14.9-4.fc17. http://koji.fedoraproject.org/koji/buildinfo?buildID=297131 Could you please test it?
Actually I'm not an user of shimbun feature in w3m-el and I'm not sure if I did correct thing for this testing though, just tried to read some articles through it on Gnus, what matching md5 in the emacs lisp. that looks good so far.
> Actually I'm not an user of shimbun feature in w3m-el and I'm not sure if I did > correct thing for this testing though, just tried to read some articles through > it on Gnus, what matching md5 in the emacs lisp. that looks good so far. Ok thanks for testing. I guess I will close this then and probably won't backport to f16.