[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: emacs 1:30.1+1-5~bpo12+1 should conflict with: elpa-eglot, elpa-project (?)



Sean Whitton <spwhitton@spwhitton.name> writes:

> Hello,
>
> On Wed 25 Jun 2025 at 04:28pm -07, Xiyue Deng wrote:
>
>> Sean Whitton <spwhitton@spwhitton.name> writes:
>>
>>> Hello,
>>>
>>> On Tue 24 Jun 2025 at 04:46pm -07, Xiyue Deng wrote:
>>>
>>>> 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.
>>>
>>> Very interesting, something like this might be indeed possible.
>>>
>>
>> Locally tested with a custom built Emacs using Provides/Breaks/Replaces
>> for Bookworm backport to be working: it tries to remove elpa-eglot when
>> upgrading to the locally built Emacs.
>>
>> I have updated my branch mentioned in Bug#1103033 accordingly.
>> Hopefully upstream will accept the new public interfaces soon so that
>> the branch can be considered to be merged.
>
> Right.  Though we'll need to wait for the trixie release unles we want
> to upload to experimental, which I'm not sure would achieve much.
>

I think this will also help with upgrading from Bookworm to Trixie.  Do
you think it's worth asking for an unblocking request?

> -- 
> Sean Whitton

-- 
Regards,
Xiyue Deng

Attachment: signature.asc
Description: PGP signature


Reply to: