| jayvdb added a comment. |
@hashar, we have used the precise sudo-less Travis images because they are much quicker to boot than the precise sudo and trusty images, and it is common for 6 job on these images to run concurrently, whereas all other images are typically restricted to 3 jobs running concurrently. Faster boot up and more concurrency = quicker elapsed build times.
However, the precise TLSv2 situation was borked on those sudo-less images (T134647: site detection test fails for proofwiki on Travis precise images before May 2015), so I pull in the sid libssl1.0.0 as of e87b9cae . It is that hack which has stopped working now.
The problem with update-locale is not new. There are many packages I would like to update on the precise images, but could not because they would drag in extra dependencies and eventually the gcc is included in the update and it fails due to locales.
Like you say, this is a chicken-egg problem *within* Debian - I havent analysed it, because I am quite sure that they are very unlikely to revise their packaging structure. The result is current sid packages often cant be installed into precise, and I expect they also can't be installed into wheezy. As wheezy is now in LTS, it is no longer part of the core Debian team's responsibilities, and so sid does not need to support wheezy/precise and it would be silly to ask the team supporting sid to fix this problem. It would be immediate "wont fix". And the LTS team also probably doesnt care about people wanting to run sid packages.
The possible paths forward:
- T132138: Perform full test suite using Wikimedia CI
- retest the Travis precise sudo-less images. The current image might not have the same problems.
- switch to Travis precise sudo images.
- switch to Travis trusty images (they are always sudo-enabled boxes; sudo-less is not possible)
- create a more targetted solution for TLSv2 on Travis, using the sudo-less wherever possible, skipping tests that need TLSv2 when on those precise images, and moving those tests that need a TLSv2 capable image to a trusty job.
- like option 5, but using Circle CI builds to do the TLSv2 testing, as Circle CI start up modern images very quickly.
Over the next 24 hrs I can investigate options 2-6, in order to find what I believe is the ideal Travis solution. This will help identify if there is an #upstream solution possible with Travis. I suspect not.
Cc: Multichill, zhuyifei1999, hashar, TerraCodes, Luke081515, Jay8g, valhallasw, jayvdb, Aklapper, Xqt, pywikibot-bugs-list, MayS, Mdupont, JJMC89, Alchimista, Krenair
_______________________________________________ pywikibot-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/pywikibot-bugs
