On Sat, Mar 15, 2025 at 1:32 PM Ihor Radchenko <yanta...@posteo.net> wrote:
> Ship Mints <shipmi...@gmail.com> writes: > > > I ran package-upgrade cherry picking org in an Emacs session that was > > running for a week or so. I restarted it after package-upgrade and got > the > > warnings below. > > > > I ran package-reinstall to force it all to be recompiled and I restarted > > Emacs with no warnings. I have a feeling what happened is that not every > > file was recompiled and perhaps there were macro expansion or something > > else that was stale. Unless there's a special step for org upgrades? Just > > guesses. > > Yes, it is usually stale macros. > Unfortunately, Emacs cannot reliably detect macro changes and users keep > running into similar issues over and over. > At least, in your case, Org detected the problem, and it did not manifest > itself in cryptic failures caused by mixing old and new code. > > The best I can suggest is installing Org mode from clean Emacs session > (with minimal config). Sometimes, cleaning elpa directory helps. > Not only for Org mode, but for other packages as well. > > > If normal ELPA update warnings/errors are more widespread, you may get > more > > noise from whatever this is due to. > > FYI, both Org and Emacs devs are trying to address this problem for the > last dozen of years. But alas, it keeps appearing because library > version management is simply not there in Elisp. > Makes sense. I wrote a lisp program to auto-populate a clean elpa tree which I occasionally run when things get crufty. Do you have a feeling for which macro(s) are the most prominent ones that cause incompatibilities from release to release?
