bug#66985: 29.1; Issue with `package.el` upgrading builtin (edge-case)

[Sylvain Bougerel <sylvain.bougerel.devel@gmail.com>]

On Sat, Nov 11, 2023 at 1:05 AM Sylvain Bougerel
<sylvain.bougerel.devel@gmail.com> wrote:
> The issue occurs in the following scenario:
>     - Package A (version a), noted A(a), depends on packages B(z), then C(y)
>     - Package C(y) depends on package B(x), which is an _older_
> version than B(z)
>     - Neither A(a), B(z) nor C(y) are installed (the state of B(x) is
> irrelevant)
>

With a bit of time (est: a week or two), I can write a unit test and
make a patch with a better commit description that follows current
guidelines. Maybe the unit test will highlight the problem better? Let
me know if that will be appropriate/appreciated. My idea for the unit
test is to show that the sequence in which requirements are enumerated
should not have an effect on the resulting transaction, while it does
at the moment (in the specific case presented below - which is the
case I will test for).

      - Sylvain