Mercurial 6.1rc0 tagged

[Manuel Jacob]

On 20/02/2022 02.03, Gregory Szorc wrote:
> I found a crashing regression when using 6.1rc0 locally. Nearly all of 
> my commands threw errors when I had obsolescence enabled.

What do you mean by “obsolescence enabled”? I do not get the error if 
the core obsolescence features (config experimental.evolution=all) are 
enabled but the evolve extension is disabled. However, I can confirm the 
error if the evolve extension is enabled (when the latest released 
version 10.4.1 is installed). It works for me with evolve 
e314f6207e5f04da921cc890cf67bb7b270c076d or later.

> The fix / 
> revert is https://phab.mercurial-scm.org/D12203 
> <https://phab.mercurial-scm.org/D12203>.
> 
> Should we ignore 6.1rc0 and tag a 6.1rc1 with the fix?
> 
> Also, I'm somewhat surprised this didn't trip any tests. Perhaps our 
> test coverage with obsolescence enabled isn't too great?

The evolve CI was failing: 
https://foss.heptapod.net/mercurial/evolve/-/pipelines/34785

> On Fri, Feb 18, 2022 at 9:00 AM Raphaël Gomès <raphael.gomes at octobus.net 
> <mailto:raphael.gomes at octobus.net>> wrote:
> 
>     Please update your package builds, thanks.
> 
>     Raphaël
> 
>     _______________________________________________
>     Mercurial-packaging mailing list
>     Mercurial-packaging at mercurial-scm.org
>     <mailto:Mercurial-packaging at mercurial-scm.org>
>     https://www.mercurial-scm.org/mailman/listinfo/mercurial-packaging
>     <https://www.mercurial-scm.org/mailman/listinfo/mercurial-packaging>
> 
> 
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel