Fwd: Dropping Support for Python 2.6

[Mathias De Maré]

(Adding Mercurial-devel mailing list, as I'm not sure if anyone is 
actually using mercurial-infrastructure@)


On 08-08-17 09:21, Mathias De Maré wrote:
>
>
> On 04-05-17 16:36, Anton Shestakov wrote:
>> 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?
> I would be willing to set this up on the existing infrastructure, if I 
> can get access to it. The CentOS builds all work now (once my CentOS 5 
> patches are in), and we are dogfooding these (not yet on a regular 
> basis, but I hope to change that). Normally, any recent Linux with 
> Docker should be enough to build these.
> I would very much like to see these builds appear in 
> https://www.mercurial-scm.org/downloads .
>
> If it's not possible to do this on the existing infrastructure, I can 
> try to set up a buildbot worker on a server in our company (but since 
> it contacts 'the world', it may take some time to get that accepted).
>
> Greetings,
> Mathias
>> _______________________________________________
>> Mercurial-devel mailing list
>> Mercurial-devel at mercurial-scm.org
>> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
>