bug#68761: [PATCH] Record dependencies in packages installed via package-vc

[Eli Zaretskii <eliz@gnu.org>]

> From: Philip Kaludercic <philipk@posteo.net>
> Cc: steven@stebalien.com,  68761@debbugs.gnu.org
> Date: Wed, 07 Feb 2024 17:07:43 +0000
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> Cc: 68761@debbugs.gnu.org
> >> From: Philip Kaludercic <philipk@posteo.net>
> >> Date: Wed, 07 Feb 2024 07:18:33 +0000
> >> 
> >> Steven Allen <steven@stebalien.com> writes:
> >> 
> >> >>> The dependency list wasn't getting recorded in the package's `-pkg.el` file.
> >> >>
> >> >> Did you notice this because of some bug or what is the motivation for
> >> >> this change?  I'll certainly look into it, I just wanted some context.
> >> >
> >> > I noticed this because I tried to remove "unused" dependencies
> >> > (package-autoremove) and ended up removing dependencies from my
> >> > package-vc packages.
> >> 
> >> That doesn't sound good.  Your patch should resolve the issue, and I
> >> would be inclined to propose applying it to the Emacs 29 branch, if the
> >> maintainers don't object.
> >
> > How serious is the problem?  Since it's unlikely there will be any
> > more Emacs 29.x releases, except if we have some emergency, we should
> > try to keep the release branch as safe and undiverged from 29.2 as
> > possible.
> 
> I wouldn't clarify it as an emergency, at most a regrettable
> inconvenience.

Then I tend to think this should be installed on master.

> Just to avoid confusion: What branch is the current release branch then?

It's still emacs-29.  When we start the release cycle of Emacs 30.1,
we will cut the emacs-30 branch.

The release branch is not closed to fixes, it just should receive only
very safe ones (like documentation fixes), or very urgent/serious
ones.