According to the discussion here:
https://www.mercurial-scm.org/pipermail/mercurial-devel/2019-April/130061...
I think maybe we may instead ask to bundle a statically linked zstd with
mercurial 4.9.
Thanks,
Neal
Neal Gompa wrote:
On Mon, Apr 8, 2019 at 8:21 AM Neal Becker
<ndbecker2(a)gmail.com> wrote:
>
> Neal Gompa wrote:
>
> > On Mon, Apr 8, 2019 at 7:36 AM Miro HronĨok <mhroncok(a)redhat.com>
> > wrote:
> >>
> >> On 08. 04. 19 13:28, Neal Becker wrote:
> >> > mercurial 4.9 packages zstd and python wrapper.
> >> >
> >> > I think we need to use system zstd. But I don't see python2-zstd.
> >> >
> >> > Is anyone working on packaging python2-zstd? It would be needed to
> >> > proceed
> >> > with mercurial 4.9. (I haven't yet checked on version number
> >> > compatibility).
> >>
> >> To add new python2 package, an exception from FPC or FESCo is needed.
> >>
> >> Can we instead update to directly to hg 5.0 in May and switch to
> >> Python 3?
> >>
> >
> > If all the reverse dependencies of Mercurial in Fedora are made ready
> > in time, we probably could. But that's still past the expected release
> > date for Fedora 30.
> >
> > Mercurial 4.9 is supposed to be Fedora 30, so I think the only thing
> > we can do is allow python-zstd in the distribution with an exception
> > to allow including a python2-zstd subpackage in addition to the
> > python3-zstd subpackage.
> >
>
> I think mercurial 5.0 on python3 is not quite ready for production use.
> I prefer to plan on mercurial 4.9 and package python-zstd, including a
> python2-zstd.
I'd like for us to ship Mercurial 5.0 on Python 3 in Fedora Rawhide
for sure. I think the six(ish) months of baking in Rawhide should be
sufficient for getting Mercurial ready to go for production use on
Python 3 and getting the reverse dependencies ported.