Sean Whitton <spwhit...@spwhitton.name> writes: > Hello, > > On Thu 03 Jul 2025 at 09:51pm -07, Xiyue Deng wrote: > >> It looks like the upstream discussion[1] may still go on for a while: >> the direction has consensus, while the details of the functions are >> still under discussion. >> >> In the meantime, I wonder whether we can move forward on the Debian side >> and have this in Trixie (with an unblock request), which will help users >> who upgrade from Bookworm avoid surprises when older versions of addons >> are installed. My branch[2] is updated to the latest version of >> upstream bug. Patches are also attached. > > I don't think the full change is appropriate for trixie, and I would > like to see the upstream changes committed to Emacs 31 before > backporting them here. > > I think though that we could add the necessary dependency relations > manually to deal with potentially broken upgrades. There is no need to > do every built-in package, right? We just need to add values for those > built-in packages that were RM'd for trixie? >
I think there are values for including other packages which helps with security updates. For example, we have Org 7.9.11 shipped with Emacs 30.1; later if a security bug is found in 7.9.11, and Emacs 30.2 ships a newer version of Org to fix that, this gets automatically taken care of by this. > -- > Sean Whitton -- Regards, Xiyue Deng
signature.asc
Description: PGP signature
