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

Cyril Brulebois <[email protected]> Thu, 26 Jun 2025 22:30:50 +0200

Newsgroups	gmane.linux.debian.backports.general
Organization	Debian
Message-ID	<[email protected]>

Hi,

Xiyue Deng <[email protected]> (2025-06-26):
> The same way.  Say someone installed elpa-eglot from Bookworm, and tried
> to upgrade to Trixie.  Now that elpa-eglot has been removed in Trixie,
> the old version will continue to exist, and cause issues.  The same goes
> for other removed packages that are bundled. It would be better to have
> them removed using this trick.

(Random backports subscriber here)

I'm not sure I'd call that a trick.

AFAICT the Conflicts/Replaces pair is pretty normal when a binary package
needs to go away (usually when its contents and/or features are merged
into/shipped by another package). Since we're talking about end-user
packages here, I assume having a Provides (versioned or not) isn't really
required (unless you want to maintain the status quo for people who would
be deploying such packages automatically, via meta packages, via Ansible,
etc.).

Not speaking for the release team, that looks like something that should
if not must be addressed to ensure smooth upgrades from Debian 12.


Cheers,
-- 
Cyril Brulebois ([email protected])            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

signature.asc (application/pgp-signature, 833 B)