Petr, I am sorry to hear of your health problems. I hope you recover soon.
I have been following this situation but have little time to spend on this.
I personally use mercurial and depend on extensions: evolve and hg-git. I
have been quiet while working on getting these extensions ported.
So far I have not taken action on moving to py3 because these 2 extensions
have not worked on py3. I'm pleased to say that as of today, evolve is
working.
hg-git is not working. I spent a little time to see if I can port myself,
but after trying a few naive fixes, it became clear that it was nontrivial
to port.
Do we have any concensus on how to proceed?
Petr Stodulka wrote:
Sorry guys
that I am disconnected last month. I had some problems with health
and now I am overbusy in work. I hoped that someone else could
continue on that meanwhile what I started.
As I pointed, you can continue with move of other packages using
the copr build anyway. But I understand that's not ideal and it should
be resolved in rawhide repos.
On 05. 10. 19 15:31, Mads Kiilerich wrote:
> 2 months later, and we still don't have Mercurial on Python 3 as an
> option in 31 or rawhide, and we can thus not do anything to move forward
> with packages that depend on Mercurial.
>
> What can we do? Offer to take over ownership of the Mercurial package?
>
> /Mads
>
>
> On 8/6/19 9:35 PM, Petr Stodulka wrote:
>> Hi guys,
>> as discussion was started week ago, Python2 is dying. As that, some
>> dependencies of mercurial will be orphaned soon (or they are already)
>> and mercurial as it is has to move in weeks on Python3. As I wrote
>> in [0], I already started some testing and investigation.
>>
>> Currently it seems that with ugly hacky fix, we are able to run
>> somi-working mercurial with Python3. I did just simple testing
>> that worked for me and in the latest copr-build (below), it seems
>> that hgk extension is workin as well. But many of you extensions
>> will be probably broken. So, I guess the most probably mercurial
>> will be broken for the others who use it.
>>
>> So it's question, should I rebase it in rawhide and setup for Python3
>> already even when it is so broken, or should I wait several weeks yet
>> for additional fixes?
>>
>> If anyone is interested about testing before it will be done,
>> just try:
>> # dnf copr enable pstodulk/mercurial
>> - it's just first attempt.
>>
>> Here is the list of RPMs depending on mercurial:
>> git-cinnabar
>> gitifyhg
>> git-remote-hg
>> gwsmhg
>> hg-git
>> hgsvn
>> hgview-common
>> python2-anyvc
>> python2-wstool
>> python3-hgapi
>> python3-wstool
>> qct-mercurial
>> rabbitvcs-core
>> rbm
>> tortoisehg
>> trac-mercurial-plugin
>>
>>
>> Cheers,
>> Petr
>
>
--
Petr Stodulka
OS & Application Modernization
IRC nicks: pstodulk, skytak
Senior Software Engineer
Red Hat Czech s.r.o.
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List
Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines List
Archives: