@lunaryorn,
It seems that epl-find-available-packages behaves differently on 24.3.1 and 24.3.50.1.
In 24.3.50.1, if you have installed a package with the most recent version available, then it will not be added to package-archive-contents when you call (package-refresh-contents). The function epl-find-available-packages checks if the package is in package-archive-contents, which it might not be.
Here's some code to reproduce the issue:
(let ((flycheck (assq 'flycheck package-alist)))
(let (package-alist package-archive-contents)
(push flycheck package-alist)
(package-refresh-contents)
(print (format "in package-alist: %s"
(not (not (assq 'flycheck package-alist)))))
(print (format "in package-archive-contents: %s"
(not (not (assq 'flycheck package-archive-contents)))))))
The package is however available in package-alist. What we could do is that we extend epl-find-available-packages so that it first checks package-archive-contents and then package-alist.
What do you think?
@lunaryorn,
It seems that
epl-find-available-packagesbehaves differently on24.3.1and24.3.50.1.In
24.3.50.1, if you have installed a package with the most recent version available, then it will not be added topackage-archive-contentswhen you call(package-refresh-contents). The functionepl-find-available-packageschecks if the package is inpackage-archive-contents, which it might not be.Here's some code to reproduce the issue:
The package is however available in
package-alist. What we could do is that we extendepl-find-available-packagesso that it first checkspackage-archive-contentsand thenpackage-alist.What do you think?