Dropping Support for Python 2.6
Anton Shestakov
av6 at dwimlabs.net
Thu May 4 10:36:17 EDT 2017
On Tue, 2 May 2017 20:30:07 +0200
Pierre-Yves David <pierre-yves.david at ens-lyon.org> wrote:
> So, we are already operating a repository at:
>
> https://www.mercurial-scm.org/release/
>
> And we already have all the necessary bits in our current make file to
> create and update it such repository. As pointed in the previous
> section, these repositories have users, since they complains when it broke.
>
> The builder use to run on some of my hardware in the USA, the thing when
> down for some time when I moved back to France (since the hardward spent
> months in cardbox). It went back online a bit last year but the build
> broken again a handful of month ago.
> I did not had time to fix it for good since then. I've been running this
> in pure good will for a couple of year but I'm not a user of it. I would
> also be happy to free the hardware for other usage. So I'm not planning
> to fix this short terms.
>
> Other member of the community (Anton for one, in CC) have expressed
> interested in resurrecting the builder. Maybe it is time to officially
> hand the thing to whoever wants to do it.
Well, it would be good to resurrect it indeed, even if because not
building RPMs anymore is clearly a step backwards.
We have a wiki page for people who want to help with running tests on
different platforms: https://www.mercurial-scm.org/wiki/Buildbot, maybe
having some clear instructions on how to set up an RPM builder would
inspire someone.
I wouldn't mind setting it up on my makeshift home server (an old
netbook with Atom CPU), the problem with that is that I don't use
RPM-based distros and don't know much about them, and dogfooding is
kinda important (e.g. people would need to ping me every time something
goes wrong, and probably include a recipe of how to fix it).
Incidentally, can't it be done on the current m-s.o infrastructure and
not by volunteers?
More information about the Mercurial-devel
mailing list