[17:06:45] [1/7] @rhinosf1 something seems to have happened with mwdeploy: [17:06:46] [2/7] ```[reception@mwtask171:~]$ mwdeploy --help [17:06:46] [3/7] Traceback (most recent call last): [17:06:46] [4/7] File "/usr/local/bin/mwdeploy", line 15, in [17:06:46] [5/7] from langcodes import tag_is_valid [17:06:47] [6/7] ModuleNotFoundError: No module named 'langcodes' [17:06:47] [7/7] ``` [17:07:29] ack [17:08:28] seems to work fine on 181 though [17:08:52] mwdeploy only works from one server anyway [17:09:06] never use mwdeploy from other than mwtask181 [17:09:38] oh, I thought it worked from both mwtask* [17:09:57] I'll stick to 181, I guess I accidentally used 171 since I've been working with that one more lately to not cause any disk size issues on 181 [17:10:34] I use task171 for mwscript and task181 for mwdeploy, idk if I should be using other task servers [17:11:00] no [17:11:06] 171 doesn't even have staging [17:11:12] so you wouldn't have got too far [17:14:55] @reception123 I suspect we switched to mwtask171 as a backup when 181 was offline or something [17:15:13] and never deleted the script [17:15:20] but maybe the packages got removed or cleaned up [17:15:35] I deleted the script from 171 so it doesn't exist anymore [17:21:32] I think too many of us main mwtask171 which could be a problem if all of us are doing stuff at the same time. [18:20:43] Done all. I hope I didn't miss a few lol