[07:09] good morning [07:37] davidcalle, do we have any news wrt deployment? [08:05] dholbach, I need to check if Mike progressed on it yesterday. Will do that in 1h, currently fixing a flat tire... [08:05] davidcalle, thanks and good luck! [08:05] Half-way between home and office :D [08:12] * dholbach hugs davidcalle [08:33] dholbach: went faster than I expected, looking at the deployment. [08:33] There have been a few changes: /me tries [08:34] davidcalle, what did we deploy where? :) [08:35] dholbach: staging/167 dependencies/28 [08:37] dholbach: ~what we merged last week + a few fixes for the deployment [08:37] and that's going to staging? [08:37] I'm just asking because of https://code.launchpad.net/developer-ubuntu-com/+activereviews [08:38] dholbach: I know, I'll merge this as soon as the ¡$%#& thing is happy :) [08:39] Yes, to staging [08:39] awesome, you're a hero <3 <3 <3 [08:39] one of the MPs will allow us to fix stuff in the store data if necessary [08:45] "distutils.errors.DistutilsError: Could not find suitable distribution for Requirement.parse('pbr>=1.8')" [08:45] hohum [08:46] I have it installed locally [08:46] maybe that's why it didn't fail [08:46] maybe time to add it to requirements.txt and to pipcache [08:46] do you have the full stacktrace? [08:46] it'd be nice to figure out what exactly requires it [08:47] can we add comments to requirements.txt? [08:47] that way we could spell out what exactly needs it [08:48] dholbach: pbr is in the dependencies branch [08:48] 1.8.1 [08:48] bizarre [08:54] dholbach: I'm adding it explicitely in requirements to see if it makes a difference [08:55] * dholbach crosses fingers [08:55] does it explode for you locally too? [09:01] dholbach: works fine locally [09:06] davidcalle, do you have pbr installed? [09:07] dholbach: I do. But I'm not sure the issue is explicitely with pbr, last week it was pilow missing in the exact same way. [09:08] hrm [09:08] can we run a local ./env/bin/python -c 'import PIL' to test? [09:09] and do we have the full stacktrace? [09:11] dholbach: sure, let me get you both [09:11] thanks [09:11] or ./env/bin/python -c 'import pbr' [09:11] dholbach: http://paste.ubuntu.com/15558242/ [09:12] dholbach: I need to wait for machines to be fully up to ssh, in ~10 min [09:13] does this indicate the dep chain? keystoneclient → positional → pbr? [09:13] davidcalle, no worries [09:14] dholbach: I'm unsure [09:14] that's how I read the log [09:22] dholbach: on the machine: no PIL, no pbr. [09:22] even though they're part of the cache? [09:22] anything in env/lib/python2.*/*-packages/? [09:23] dholbach: and running "pip install --exists-action=w --download pip-cache/ -r requirements.txt" on the machine, with a full pip-cache/, tries to download eg. beautifulsoup4 [09:23] which pip version is it? [09:23] 1.5.4 [09:24] Wow, just checked the version I'm running locally [09:25] maybe it needs a newer pip(?) [09:27] pip-cache has pip-7.1.2-py2.py3-none-any.whl [09:27] so that's not used either [09:42] dholbach: there is no pip in the cache [09:49] davidcalle, it was removed in the meantime [09:49] dholbach: should I try to add it to requirements? [09:50] it was removed in r27..28 [09:50] I don't know if it's going to help [09:51] but maybe worth a try? [09:52] dholbach: yeah, trying [10:25] dholbach: I've tried several variations, without luck. I'm repushing the latest deployable version on staging. Let's not block importer fixes anymore. Do some of your changes require a components upgrade? [10:25] no, not necessarily [10:29] dholbach: looks like pip-cache install passed fine. I don't know if it's due to a specific new version of a component not working well on trusty or the lightweight checkout. If it's the latter, maybe we can use lightweight checkout only in a "make dev" context? [10:29] hohum... I thought that was the case [10:30] dholbach: looks like you are right [10:31] dholbach: then, it's something else. Either a component that has been removed and is somehow essential in our staging stack or a buggy one. [10:32] davidcalle, maybe ./env/bin/python -v -c 'import PIL' [10:32] and ./env/bin/python -v -c 'import pbr' [10:33] dholbach: I'll try it [10:33] * davidcalle lunch, see you in a bit :) [10:33] enjoy [11:11] Hey everyone [11:12] I was wondering .. does anybody know what type of bluetooth keyboard and mouse are used for the Ubuntu tablet presentation on ubuntu.com/tablet ? [11:12] And if not .. who would be able to answer that question? :) [13:03] Moe: good question. Worth asking in #ubuntu-touch. [13:26] davidcalle: I did, they didn't no any specifics .. I was wondering about who to contact at Canonical concerning this :) [13:26] *know [13:29] Moe: the best person would probably be yaili, who designed the page (see: http://design.canonical.com/2016/02/a-new-look-for-tablet/), she often comes in this chan, but she doesn't seem to be around today [13:33] davidcalle: That's great, thank you for the pointer <3 [13:33] maybe just send a mail to the mailing list? [13:34] I'll do that as well, cheers [13:34] Is it active though? The last email to the list shows as May 2015 [13:37] Moe: ubuntu-phone@lists.launchpad.net is the most active one [13:45] Ah, that one's different from the link in the topic .. I guess? [13:46] Moe, this channel is about the website [13:48] Ah right, sorry, I didn't see the obvious difference [13:48] My bad [13:51] no worries :) [14:02] davidcalle: dholbach: was there a need to update the pip requirements after the last deployment? [14:03] one of them is giving me all kinds of trouble during deployment [14:04] mhall119: dholbach told me there wasn't, so I'm about to strip these changes. For now, I'm renewing the security cert of the site [14:04] mhall119: *I"m about*, well, that's the plan, but if you have another idea... :) [14:06] davidcalle: I'm working on staging atm, so please hold off on making any changes [14:06] I've already done some work on the spec and dependencies branch [14:07] mhall119: ok, note that I've downgraded staging to a working version, you need to change collect values and redeploy [14:07] davidcalle: when did you do that? [14:08] mhall119: this morning, which allowed to discover that our security cert is expired [14:09] (see #is) [14:10] I love the "Oh yeah, that's something you guys are responsible for, surprise!" [14:10] yep [14:11] Reading the doc and still trying to figure out the value of $cn. Hint, it's not "developer.staging.ubuntu.com" [14:11] Anyway, I'm logging out of wendigo, good luck :) [14:12] should change the motd on wendigo to "Abandon all hope, ye who enter here" [14:17] :D [19:40] mhall119: any luck with wendigo? [19:51] I'm trying to unknot the problem with our deps [19:52] one of them is trying to pull in another dep, but it's always trying to get it from pypi.org rather than pip-cache