Sean Whitton <spwhitton@spwhitton.name> writes: > Hello, > > On Sat 21 Jun 2025 at 05:36pm +02, Micha Lenk wrote: > >> Hi Sean, >> >> >> >> Am 20. Juni 2025 18:08:31 MESZ schrieb Stefano Zacchiroli <zack@debian.org>: >>>Heya, after upgrading (a while ago) to the Emacs backported version in >>>subject, I've faced a number of issues with IDE-like features, which >>>took me a while to understand and fix. The symptom was eglot failing to >>>start (due to undefined variables). The fix was to remove the separate >>>packages elpa-eglot and elpa-project, making happy their now integrated >>>counterparts in Emacs core. I haven't investigated this any deeper than >>>this, but I thoughts you might want to hear about this and consider the >>>adding an explicit Conflict from Emacs to these two packages (at least), >>>to avoid similar issues for other users. >> >> In March you helped with backporting dh-elpa, so, do you have by chance some >> knowledge or advice how to cope with that situation best? > > This is a longstanding problem with Emacs addons in Debian. The > separately packaged versions always override the ones in Emacs core. > Our solution for now is just to keep the separately packaged versions > up-to-date. > As we are working on Bug#1103033, I wonder whether it's possible for Emacs to replace those eternal packages if the built-in packages are of higher versions. I wonder whether it's doable by using provides/breaks/replaces. Take eglot as an example: currently bookworm has 1.9-2. Say if Emacs has the following: ,---- | Provides: elpa-eglot (= 1.15) | Breaks: elpa-eglot (<< 1.15) # Or maybe Conflicts? | Replaces: elpa-eglot (<< 1.15) `---- it would hopefully uninstall elpa-eglot 1.9-2 from bookworm when upgrading Emacs. > -- > Sean Whitton -- Regards, Xiyue Deng
Attachment:
signature.asc
Description: PGP signature