[00:36:06] is it just me or did git::clone become extra sluggish recently on vagrant? [00:38:47] I haven't been cloning many new things to notice. I can't think of anything that would have changed in mw-v around that. Maybe your havig trouble talking to gerrit? [00:44:17] cloning from gerrit is in general always continuously becoming slower [00:44:36] and sometimes, it becomes discretely faster when someone runs `git gc` on the repos. [00:44:41] git::clone requires package[git] and that triggers an apt update which seems to be the culprit [00:45:07] cloning mediawiki was always slow but I ran into this for some small repos [00:46:11] apt cache is shared over NFS, right? [00:46:19] I wonder if that is making it slow somehow [01:16:36] tgr: is there an upgrade or install or just the update? [01:45:55] AaronSchulz: just the update [01:46:06] it runs in a few seconds when I update it manually though [01:55:27] bd808: do you think it would cause problems if we installed pip via pip on vagrant? [01:55:45] ubuntu pip is at 1.5.4, pip pip is at 7.1 or something like that [01:56:47] there are some backwards-incompatible changes in the requirements.txt format between the two [02:02:13] tgr: dunno. are there things in the newer pip that are must haves for something you are working on? [02:03:23] also no package should continually trigger an apt update. If that's happening we need to fix it [02:03:36] Puppet should update apt at most once per day [02:07:34] bd808: I'm trying to add a pywikibot role, and pywikibot's requirements file needs pip6+ [02:07:55] there are a number of workarounds if we don't want to update the system pip [02:08:32] is there a good reason why it needs pip6+, or could it be ported to an older format without loss of functionality? [02:08:39] if the latter, then i'd consider doing that and submitting it upstream [02:08:43] put it in a virtualenv, or install the newer pip with --user, or just ask pywikibot people to supply another requirements file [02:08:55] it uses markers [02:09:10] somePackage ; if python < 3 [02:10:17] nice, branching [02:10:22] no S-expressions yet [02:11:10] we could provide a newer pip package via apt.wikimedia.org [02:13:34] https://pip.pypa.io/en/latest/news/ lists the backward-incompatible changes; they don't seem too scary [02:17:38] not sure how pip is used around the cluster; for me just upgrading it on vagrant would be fine