[07:34] good morning [08:41] Morning o/ [09:05] salut davidcalle [09:05] how's the deployment situation? :-) [09:05] dholbach: I'm testing db migrations on staging [09:05] :) [09:06] dholbach: I don't remember how to set up postgre locally for d.u.c, do you still have that doc somewhere? [09:07] (because, currently, it's exploding here and there :) ) [09:13] dholbach: btw, since you have more experience that I do with django migrations, if I pass you the dbdump file, do you think you can give it a try? [09:18] hum... yes - I can try [09:20] http://pad.ubuntu.com/zdvmD4Ekb6 [09:36] dholbach: thanks, I'm getting the db file from the server, it's taking some time [09:37] sure, thanks! [10:24] davidcalle, I started with lp:developer-ubuntu-com/production [10:24] is that what's on prod? [10:25] dholbach: on prod, due to issues when using several branches (bzr doesn't want to merge cleanly) we have staging/162, hopefully this will get back in line after the next prod deployment [10:25] ok [10:26] * dholbach starts over [10:27] the update will be (for now at least) to r164 (which is the big upgrade without post-deployment-fixes). [10:33] ok [10:38] dholbach, davidcalle, victorp was pinging me about adding installation instructions for the snappy image of intel's thincanyon. But as far as I can see, they're live already, right? https://developer.ubuntu.com/en/snappy/start/ [10:38] intel nuc? [10:39] I thought they were the same thing [10:40] I have no idea [10:40] thibautr and didrocks published the docs [10:40] let me ask [10:40] looking at the history of the page, davidcalle did the changes [10:40] oh ok... I thought it was thibaut and didier in the beginning [10:40] ah wait, no perhaps didrocks [10:41] misread the history [10:41] ^W^W^W^W^Wa team of French people [10:44] :) [10:44] davidcalle, so I updated http://pad.ubuntu.com/zdvmD4Ekb6 and tried to explain how I went about things - I'm still in the process of figuring out the migrations story [10:45] meanwhile didrocks wants a call, so I'll brb [11:18] dholbach: thanks! [11:19] dpm, dholbach, tell me when you know if the nuc page is the one you were looking for. I'll prettify it. [11:29] davidcalle, that's the one, yes [11:29] davidcalle, I'm not quite sure what the question about it was.... [11:29] dpm, dholbach, thanks, the question is somehow irrelevant to me, the page is screaming for a fix :) [11:30] go go go! [11:58] dholbach: I'm giving your doc a try. Huge thanks for writing it. [12:00] davidcalle, I'm not done yet :) [12:00] the tricky part is coming up now [12:01] and I'll do it after lunch [13:47] davidcalle, can you try to replay http://pad.ubuntu.com/zdvmD4Ekb6 locally? [13:47] I'll do it as well [14:04] dholbach: on it [14:04] maybe we can talk with Mike later on when he's back [14:04] and see if there's anything we can do to the migrations process [14:17] dholbach: pip-cache timed out :D [14:18] wow [14:18] that has never happened to me [14:18] I guess if you want to work around it, just ./env/bin/pip install -r requirements.txt --upgrade [14:22] it was probably my vpn acting up, seems to work fine now [14:25] <3 [14:27] * davidcalle hugs dholbach [14:27] * dholbach hugs davidcalle back [14:28] davidcalle, I'd like to be sure we covered everything with the migrations which are faked or really run [14:28] dholbach: it WORKS, great work ! [14:28] watching it break is not so nice :) [14:28] but I haven't found a way to work around it [14:28] mhall119, can you take a look at http://pad.ubuntu.com/zdvmD4Ekb6 too? [14:29] ... and see if it's OK and how you'd expect it? [14:42] dholbach: what we need to make sure is to have a way to answer "yes" to deletion of the stale migrations. The juju way of doing it doesn't work well with interactive prompts and "migrate --noinput" just ignores the question. Maybe something like http://stackoverflow.com/questions/18869414/can-stale-content-types-be-automatically-deleted-in-django [14:43] good point [14:54] dholbach: why are we editing settings.py? [14:55] actually, let's go back further, what is all this for? [14:59] mhall119: local upgrade testing with postgre [15:01] oh, I see [15:02] mhall119: I wanted Daniel's help for his expertise on migrations [15:04] is rev 163 or 164 when the upgrade happened? [15:13] mhall119: 163 [15:14] 164 is a fix that was missing to adapt to newer swift [15:24] ok [15:26] it looks reasonable, has it been tested? [15:27] davidcalle: on line 19 you install django, but shouldn't that be installed by pip so we get a specific version? [15:28] dholbach: ^ [15:28] my only other concern would be a difference in postgresql versions between your localhost and staging/prod, but that's less likely to cause problems than Django [15:42] mhall119, I copied it from README [16:11] right, that's probably old and unnecessary now