[08:11] <dholbach> good morning
[08:13] <dholbach> davidcalle, fantastic work getting the new rev deployed
[08:22] <davidcalle> dholbach: to you too!
[08:30] <dholbach> davidcalle, I might push another branch updating a few smaller components (and try to keep them up to date)
[08:31] <davidcalle> dholbach: thanks! I'll get started on pushing the updated template as well
[09:06] <dholbach> done, https://code.launchpad.net/~dholbach/developer-ubuntu-com/update-components/+merge/289867
[09:06] <dholbach> AFAICS it all works well
[09:06] <dholbach> and gets us security fixes and other stuff
[09:09] <dholbach> it's updating everything apart from django 1.9
[09:09] <davidcalle> dholbach: zinnia still doesn't work with django 1.9, right?
[09:09] <dholbach> there are a couple of things where we see deprecation warnings
[09:10] <davidcalle> yep
[09:13] <dholbach> davidcalle, it looks like the newer django cms requires other cache durations to be set as well, or it explodes with KeyErrors
[09:13] <dholbach> I picked 60 as the cache duration for content as it seems to be the default
[09:13] <dholbach> permissions should probably never be cached(?)
[09:13] <dholbach> I don't know
[09:16] <davidcalle> dholbach: maybe we could follow the defaults here? http://docs.django-cms.org/en/3.2.3/reference/configuration.html#cms-cache-durations
[09:17] <dholbach> oh ok
[09:17] <dholbach> yes, that makes sense
[09:17] <dholbach> the only thing was menus, which was set to 0 before
[09:18] <dholbach> maybe as a workaround if added articles don't show up(?)
[09:18] <davidcalle> I have no idea :)
[09:18] <dholbach> that was part of rev1
[09:18] <dholbach> but yeah, let's go with the default for permissions
[09:19] <dholbach> awesome
[09:21] <davidcalle> In any case, I'm +1 on the general upgrade. I'll push it to the staging server asap (especially to test these new versions of swiftclient, keystoneclient, etc.)
[09:21] <dholbach> cool
[09:22] <dholbach> for the new pillow to compile one needs to have libjpeg-dev installed locally
[09:23] <dholbach> but that's the only other caveat I could see
[09:23] <davidcalle> dholbach: about dependencies, should we simply empty the branch and run update-pip-cache from trunk?
[09:25] <davidcalle> dholbach: do you mind specifying it in the mp description? (libjpeg-dev)
[09:26] <dholbach> davidcalle, or how about this http://paste.ubuntu.com/15478269/?
[09:26] <dholbach> davidcalle, sure, will do
[09:29] <davidcalle> dholbach: yes, but I actually don't see a huge difference in time, do you?
[09:30] <davidcalle> (at least when I tried yesterday)
[09:30] <dholbach> you're right
[09:31] <davidcalle> dholbach: also, I don't think I've really understood Mike's concerns about cleaning the branch
[09:31] <dholbach> in that case we should probably go with your suggestion - I'm just wondering if old branches or old installs will fail or have problems?
[09:31] <dholbach> or we could create a new branch and call it dependencies2016 :)
[09:31] <dholbach> and do a new one next year :)
[09:32] <dholbach> it'd be a poor man's logrotate for pip dependencies
[09:32] <davidcalle> dholbach: hah, here is one case where git would be easier to deal with than bzr :)
[09:33] <dholbach> was your idea to push --overwrite to the current branch with a new r1?
[09:33] <dholbach> that's right :)
[09:35] <davidcalle> dholbach: nope, having a r22 with only the packages we care about (that would probably need lightweight checkout to actually be lighter, though)
[09:36] <dholbach> but the old revision history is still going to be there
[09:42] <davidcalle> dholbach: I'm on board with any idea that brings the downloading size down: right now we only need ~40MB of packages
[09:43] <dholbach> let's clean the branch and see if a lightweight checkout helps
[09:43] <dholbach> shall I do this?
[09:45] <davidcalle> dholbach: alright, I'm doing the staging tests for the new deps on my end
[09:49] <davidcalle> dholbach: I need to update the deps branch right now, is that fine with you?
[09:50] <davidcalle> Hah, you did it :)
[09:53] <dholbach> still working on it
[10:01] <dholbach> davidcalle, pushed the latest - let me know if it works for you
[10:02] <dholbach> davidcalle, shall I push the lightweight change too?
[10:03] <davidcalle> dholbach: yep
[10:03] <dholbach> pushed
[10:04] <dholbach> oh ok
[10:04] <dholbach> you merged update-components already
[10:04] <dholbach> let me re-propose it :)
[10:05] <dholbach> https://code.launchpad.net/~dholbach/developer-ubuntu-com/update-components/+merge/289875
[10:05] <dholbach> davidcalle, ^
[10:10] <davidcalle> dholbach: merged :)
[10:13] <dholbach> yeehaw
[10:13] <dholbach> now let's see how this works with a fresh checkout
[10:15] <dholbach> 1m15s for 'make env'
[10:15] <dholbach> and 40M pip-cache
[10:15] <dholbach> I would call this a success :-)
[10:16] <davidcalle> \o/
[10:20] <dholbach> davidcalle, mhall119: shall we have bets on how long it'll take to land the newest changes?
[10:20] <dholbach> dpm, ^ :)
[10:22] <davidcalle> dholbach: with the right urgency set to the rt and potential unwillingness to do it on a friday, I'm betting on monday :)
[10:24] <dholbach> so you want to push this today?
[10:25] <davidcalle> dholbach: if the staging deployment is fine, yes
[10:25] <dholbach> cool
[10:28]  * dpm reads scrollback
[10:28] <dholbach> dpm, you don't have to read all of it
[10:29] <dholbach> dpm, I was just asking if we should have a bet on when the next deployment lands :)
[10:29] <dholbach> how long it's going to take
[10:29] <dpm> ok ok :)
[10:30] <davidcalle> dpm: dholbach: staging deployment started
[10:31] <dholbach> awesome
[10:35] <dpm> cool
[10:37] <dpm> moving back here for website talk :) - davidcalle, what exactly landed in last night's prod deployment, and which branches do we now have pending to land?
[10:42] <davidcalle> dpm: Django upgrade to 1.8, CMS upgrade. Pending to land (merged in trunk): APIdoc frameworks fixes, first pass at importer changes for snappy overhaul (didrocks new IA), general deps update
[10:44] <davidcalle> Not in trunk yet: more fixes for snappy doc import
[10:51] <dpm> thanks a lot davidcalle
[13:10] <mhall119> davidcalle: dholbach: are we going to work on the next deployment in staging today?
[13:43] <davidcalle> mhall119: I've started, staging currently claims there is a missing dep in the dependencies branch (Pillow 3.1.0), but it's in there. Looking at it.
[14:03] <dholbach> davidcalle, the MP I pushed is not important - we can add it whenever it's convenient
[14:04] <davidcalle> dholbach: once I'm done with a call and staging initial deployment, I'll have a look, no worries :)
[14:04] <dholbach> davidcalle, basically just an update of the test data of the importer (so we're closer to reality)
=== JoseeAntonioR is now known as jose
[15:48] <dholbach> mhall119, do you know why we have Pillow in the requirements.txt?
[15:53] <mhall119> dholbach: probably the image plugin for django-cms needs it
[15:54] <mhall119> or zinnia
[15:54] <dholbach> mhall119, I'm just wondering because it's explicitly listed in requirements.txt
[15:55] <mhall119> you think it should be removed and just assumed from the dependencies of other packages?
[15:56] <dholbach> normally pip would just take care of it
[15:56] <mhall119> requirements.txt was generated from calling `pip freeze` after installing everything and then stripping away stuff I thought was brought it via dependency
[15:56] <mhall119> dholbach: I'm +1 with removing it and seeing what happens
[15:57] <dholbach> mhall119, oh ok... I didn't know about pip freeze
[15:57] <dholbach> it's just that I was going through the list again, just to keep up to date
[15:57] <dholbach> if there's just stuff in there we care about, that's obviously easier then
[16:07] <dholbach> davidcalle, https://code.launchpad.net/~dholbach/developer-ubuntu-com/update-components/+merge/289937
=== ubott2 is now known as ubottu
=== daker_ is now known as daker
=== pleia2_ is now known as pleia2