Last modified: 2013-11-06 16:58:42 UTC
In order to build the puppet script for deploying LaTeXML a debian package was build https://gerrit.wikimedia.org/r/#/admin/projects/operations/debs/latexml that should be submitted to the mediawiki apt repository. Unless this is done the development of https://gerrit.wikimedia.org/r/#/c/61767/ (from 1st of may 2013) is blocked.
I'm not sure which section this should go in, but it's not related to git-deploy.
The packages maintained in Gerrit under operations/debs/* are build by the operations team which then upload the packages on apt.wikimedia.org. You can ping some of them on IRC: #wikimedia-operations Since ops usually DO NOT look at bugzilla. You will want to use their mail based tracking system by sending an email to ops-requests@rt.wikimedia.org
I already tried both methods and used that email. But I didn't get a reply.
(In reply to comment #3) > I already used that email. But I didn't get a reply. Ticket was successfully created: RT #5743
I believe that...However I can not see that;-)
Maybe someone can explain to what it means to upload the package? If it's a lot of work it might be faster for me to create an own repository?
(In reply to comment #6) > Maybe someone can explain to what it means to upload the package? Whenever a package under operations/debs has been changed, someone from ops has to fetch it on a build machine, create the package and upload it on apt.wikimedia.org. When the package has been properly tested on labs under Ubuntu Precise, its probably less than half an hour to achieve the process. To prevent anyone from getting root access on the cluster via a malicious package, only Wikimedia roots are allowed to upload a package on apt.wikimedia.org, most of them are part of the operations team which use RT as an issue tracker. So the process is roughly: 1) fill a RT 2) ping ops folks in #wikimedia-operations 3) repeat Even internally, it usually takes me a few weeks to get any package uploaded there. > If it's a lot of work it might be faster for me to create an own repository? You can also upload the package on launchpad.net :-) They have the concept of ppa repositories which are more liberal and publicly available. That being said, if the package has to land on the Wikimedia cluster, it MUST be uploaded on apt.wikimedia.org.
ok. I think the solution is to use a puppet script. I made one for vagrant. That should be easy to port to operations. https://gerrit.wikimedia.org/r/#/c/86420/
(In reply to comment #4) > Ticket was successfully created: RT #5743 RT ticket got resolved: "afaik this ticket regaring the latexml package is outdated, i just briefly talked to Gabriel as well and saw some mail threads, turns out the Node.js solution is 10x faster etc and runs in the browser sandbox and this is not the preferred solution anymore. So i'm closing this ticket."
It's unclear to me how to move forward (or if this ticket is still needed). Could somebody clarify, please?
The software needed for displaying MathML at Wikipedia is no longer meant to be LaTeXML. Currently, the new (mathoid) solution requires the following commits to be merged 1 https://gerrit.wikimedia.org/r/#/c/90733/ 2 https://gerrit.wikimedia.org/r/#/c/90748/ 3 https://gerrit.wikimedia.org/r/#/c/85801/ (4) https://gerrit.wikimedia.org/r/#/c/87479/ (optional) Merging all this commits would not change anything for the wikipedia user. After the the option allow MathML can be switched on, which allows the logged in user to use the mathml+svg rendering mode. After that it could be defaulted if the user experience is positive. The sad thing is, after I left SFO and went back to Berlin almost nothing has happened and unfortunately nobody from the foundation is assigned to this task so I have doubts that anything will happen in the future. So there is a potential risk that it will take another 10 years until MathML gets live. That's background information concerning the question how to move forward. Regarding 1 https://gerrit.wikimedia.org/r/#/c/90733/ the question is how to deploy the node request module. I used node and phantomjs the first time in the context of the texvc2MathML conversion. But as far as I have understood it would be sufficient to store the js source of the node request module in some folder and copy it to the modules dir of the node installation. But this seems more like a hack to me.... So I have no idea what I could do to make progress on 1 In the long term, we could want to have math search (http://demo.formulasearchengine.com/index.php/Special:MathSearch?mathpattern=\sin%28?x^2%29) we would want to have LaTeXML
update: (4) was merged into 1.22.
