/srv/irclogs.ubuntu.com/2015/10/23/#ubuntu-ci-eng.txt

michi__robru: ping01:37
robrumichi__: hey what's up?02:36
=== chihchun_afk is now known as chihchun
michi__robru: Thanks for your reply, all sorted out. (Sorry, didn't see your message earlier).02:56
=== chihchun is now known as chihchun_afk
michirobru: I really like the change in color scheme when a silo is dirty. Thanks for that, nice touch!05:00
robrumichi: you're welcome05:42
=== chihchun_afk is now known as chihchun
abeatorobru, hi, would it be possible to clean the wily packages in silo 13?07:53
robruabeato: sure one sec07:53
abeatorobru, ok, thanks07:53
robruabeato: done! you're welcome07:54
abeatogreat07:54
Saviqrobru, hey, can I reset the dirty flag somehow https://requests.ci-train.ubuntu.com/#/ticket/445 ? we've reverted the commit that caused it to go dirty (was a trunk merge anyway)08:21
Saviqrobru, otherwise, will this cause us trouble on publish?08:21
robruSaviq: hmmm08:21
robruSaviq: the file that tracks commit IDs would indeed match again if you reverted the commit, but the dirty flag can officially only be removed by doing an actual rebuild. however I can go in and surgically remove the flag from the silo08:23
Saviqrobru, no need if it will allow us to publish08:25
robruSaviq: I cleared the flag manually and I'm doing a WATCH_ONLY build to make sure that the commits all match expectations08:26
Saviqrobru, tried a watch_only yesterday and it didn't work, it was, though, before the revert08:26
robruSaviq: yes, but I waved my magic wand prior to running WATCH_ONLY though.08:27
Saviqrobru, ah ;)08:27
Saviqrobru, I think it'd make sense for watch_only to re-check the commit ids08:27
robruSaviq: yeah this needs a bit of work. the problem is that dirtiness can be created either by new commits or by other silos being published and it's not currently possible to tell which is which.08:28
Saviqrobru, ack08:28
robruSaviq: I'll file a bug for now08:28
* Saviq waiting for brendand to rise from the dead and give some feedback on silo 22, shame it won't merge/clean until migration for xenial is on anyway...08:30
Mirvsil2100: ok, we were here :)08:31
robruSaviq: here you go https://bugs.launchpad.net/cupstream2distro/+bug/150925008:33
ubot5Launchpad bug 1509250 in CI Train [cu2d] "Allow people to uncommit new commits." [Medium,Triaged]08:33
Saviqbrendand, morning! any news on silo 22, you've been awfully quiet :)09:34
brendandSaviq, i spoke to kgunn yesterday. i had some unrelated issues, then found out i had the wrong citrain version09:36
brendandSaviq, testing it now09:36
Saviqack09:46
Saviqbrendand, no pressure at this point, as we're blocked by lack of proposed migration for xenial09:47
Saviq+anyway09:47
=== oSoMoN_ is now known as oSoMoN
oSoMoNubuntu-qa: is silo 16 on someone’s plate? ToyKeeper wasn’t able to confirm the desktop fixes10:00
=== lan3y is now known as Laney
=== rsalveti_ is now known as rsalveti
=== plars_ is now known as plars
oSoMoNrvr, thanks for the comment. One of the fixes in silo 16 is desktop-specific (fixes a crash). Of course I verified it myself, is that enough? If so can you/someone please approve the silo?10:24
oSoMoNthe fix in question is for bug #150805410:25
ubot5bug 1508054 in webbrowser-app (Ubuntu) "[desktop] Crashes on startup" [Critical,In progress] https://launchpad.net/bugs/150805410:25
rvroSoMoN: Yes, I think so10:35
rvroSoMoN_: Silo 16 approved10:51
=== davmor2_ is now known as davmor2
jgdxtrainguards: when building against xenius+vivid, i get that pep8 isn't installed: https://launchpadlibrarian.net/222250573/buildlog_ubuntu-xenial-amd64.ubuntu-system-settings_0.3%2B16.04.20151023-0ubuntu1_BUILDING.txt.gz11:04
oSoMoN_rvr, thanks11:05
jgdxtrainguards: sorry, it's not installable, rather.11:06
Mirvcoincidentally I was just upgrading my chroot:s and lxc:s to xenial11:09
Mirvjgdx: it says to me that pep8 depends on python3-pep that is no longer available, so it errors out11:09
jgdxcan I land using vivid+wily?11:10
robruMirv: jgdx looks like there's already a fix in xenial-proposed, not sure when that'll land11:10
Mirvjgdx: well, it's fixed actually in this https://launchpad.net/ubuntu/+source/pep8/1.6.2-0.1ubuntu1 that is in xenial-proposed, and our PPA:s should be using prpoposed11:10
Mirvjgdx: no, wily is no more, other than SRU:s11:10
Mirvrobru: shouldn't our PPA:s build with proposed anyway?11:10
jgdx(weird way of adding plural to these things, Mirv :P)11:10
Mirvbut it might be xenial is not completely "running" yet11:10
robruMirv: hmm, I think so...11:11
jgdxMirv, is there a way to know for sure if that's fix is in?11:11
jgdxMaybe let me know/enable me to know so I can start another build?11:11
Mirvrobru: hey Mr. 4am, haven't we talked about this?11:12
robrujgdx: what silo?11:12
robruMirv: shush you11:12
sil2100The builders are probably not using -proposed11:12
robru;-)11:13
sil2100I mean, the builder build-envs, as it seems to die out on very early stages of the build11:13
jgdxrobru, the silo's under your pillow! Go get it ;P11:13
jgdxrobru, 3911:13
Mirv039 it'd seem11:13
Mirvit has proposed enabled11:13
sil2100We might need to wait for it to migrate11:13
robruHmm I don't have my lp login on this tablet...11:16
robruOK I'll let you guys figure it out ;-)11:16
robruGoodnight11:17
sil2100Goodnight11:21
sil2100I didn't create a xenial chroot yet as I know it's a bit early yet11:21
brendandSaviq, can you clarify how to test this ? https://bugs.launchpad.net/ubuntu-translations/+bug/137206111:33
ubot5Launchpad bug 1372061 in unity8 (Ubuntu) "SMS notification: time format not translatable" [High,In progress]11:33
brendandSaviq, the notifications indicator no longer seems to use date stamps11:33
brendandSaviq, it just says x minutes/hours ago11:33
Saviqbrendand, yeah, we've just deleted a bunch of code and reverted to what SDK now provides11:58
=== alan_g is now known as alan_g|lunch
Saviqbrendand, so if it looks right... it's right11:58
Saviqdednick, unless you have an idea to test ↑↑11:58
dednickSaviq: no, it should just be the same11:59
Saviqbrendand, basically, the fix comprised of implementing The Right Thing™ in the UITK, now we've switched to using it - if it's in the UITK, it has to be good, right? :)12:02
Saviqand the translation comes from there as well12:03
brendandSaviq, yeah it seems good12:03
brendandSaviq, i had to adjust the clock manually to make it show a date12:03
=== popey_ is now known as popey
Saviqack12:06
=== _salem is now known as salem_
oSoMoNkenvandine, hey, would you mind acking the packaging changes in silo 16? https://ci-train.ubuntu.com/job/ubuntu-landing-016-2-publish/121/artifact/webbrowser-app_packaging_changes.diff12:44
kenvandinesure12:45
kenvandine+1 from me12:45
kenvandineoSoMoN, want me to publish it?12:45
oSoMoNkenvandine, if you don’t mind12:46
kenvandineoSoMoN, published12:47
oSoMoNthanks!12:47
kenvandinenp12:47
=== alan_g|lunch is now known as alan_g
jgdxMirv, how we doing wrt the pep8 package?13:01
Mirvjgdx: please join #ubuntu-devel , there might be related discussion soon13:11
bfillerkenvandine, renatu : re: silo 19, does this need to be dual landing? I wasn't sure whether buteo was in wily or not and it's status in x13:12
kenvandinebfiller, i think it's in xenial now13:13
kenvandineso dual landing would be xenial+vivid13:13
kenvandineso should be fine13:13
bfillerkenvandine: ok thanks13:13
kenvandinenp13:13
Mirvjgdx: I just figured something when I was about to ask there... just a moment13:15
Mirvsil2100: FYI bug #150935613:16
ubot5bug 1509356 in pep8 (Ubuntu) "pep8 depends on python3-pep, not python3-pep8" [Undecided,New] https://launchpad.net/bugs/150935613:16
MirvI figured out when I stared at the diff again.. the builders _are_ using proposed correctly, and that's the problem13:17
rvrdbarth: Approving silo 5613:39
oSoMoNtrainguards: is it expected that packages for the X series are landing in the overlay PPA, not in the distro?13:39
MirvoSoMoN: that's an error in ticket configuration if that happens13:40
Mirvthe target PPA field should be empty13:41
oSoMoNMirv, well I had silo 16 that was awaiting QA validation before robru enabled X in bileto, so I asked him to manually binary-copy the wily packages to retarget xenial in the silo, and I was expecting they would land in the correct place13:41
oSoMoNMirv, it was a dual silo, initially targetting vivid and wily, then modified to target vivid and xenial13:42
MirvoSoMoN: the binary-copy is needed, but so is ensuring the PPA field is empty so it does the normal dual thing ie vivid to PPA, devel to archive13:42
MirvoSoMoN: so yes https://requests.ci-train.ubuntu.com/#/ticket/547 had the field13:42
MirvoSoMoN: we'd need a core-dev to copy it from the overlay to archive and then we can delete the overlay version13:43
oSoMoNah, I didn’t know that, I thought the field was needed for the vivid packages to go to the PPA13:43
oSoMoNkenvandine, could you do that for us? ^^13:43
MirvoSoMoN: no, the behavior is "known" but I agree not obvious.13:43
Mirvah, right it's the time when Ken is around :)13:43
kenvandineoSoMoN, which silo?13:48
oSoMoNkenvandine, the one you published an hour ago :) I didn’t know but it was targetted at the overlay PPA for the X series, so we need to copy it from the silo to the distro proper, and delete the X packages in the overlay PPA13:52
Mirvkenvandine: so copy-package webbrowser-app from overlay xenial to archive xenial13:53
Mirvs/archive xenial/archive xenial-proposed/13:53
kenvandineah13:53
dbarthrvr: \o/ thanks13:56
kenvandineoSoMoN, Mirv: done14:00
kenvandineMirv, should i delete the xenial build from the ppa?14:01
oSoMoNkenvandine, thanks!14:02
Mirvkenvandine: thanks! and thanks for also deleting it from the ppa.14:14
kenvandinenp14:14
Mirvsee you in a week, everyone14:15
Mirvrobru: sil2100: the 024 xenial is still in abyss, not sure what happened, rsync seems correct14:17
sil2100Mirv: have a nice holiday!14:22
Mirvsil2100: thanks!14:29
=== salem_ is now known as _salem
=== _salem is now known as salem_
brendandSaviq, all clear14:56
Saviqbrendand, \o/14:59
Saviqkgunn, greyback ↑15:00
Saviqtrainguards, we'll need to transition silo 22 to xenial, please15:00
kgunngreatness15:00
* kgunn sheds a tear and whispers "good bye" silo015:01
Saviqright :D15:01
Saviqit took us under a year to go from silo0 to release :D15:01
sil2100hmmmm15:03
sil2100Saviq: ok, performing the binary package copy15:03
greybackSaviq: kgunn woooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo15:03
greybackoh if only I didn't have to drive now15:03
greybackSaviq: has it really been a year?15:06
kgunngreyback: almost...10 mo for sure15:08
kgunnalmost like a baby15:08
Saviqgreyback, MWC last year15:16
Saviqerm *this* year15:16
greybackblimey15:16
jibelbfiller, Kaleo ^ camera app approved you can publish. It won't break on devices running stable?15:56
bfillerjibel: it shouldn't but we'll test, there is problems with that silo though won't build on xenial15:57
Kaleobfiller, stable has 1.3 right?15:57
bfillerKaleo: yes it does15:57
Kaleocool15:57
jibelbfiller, I'm sanity testing on stable15:58
jibelKaleo, it does, it shouldn't be a problem, but I just want ot make sure15:58
bfillerKaleo, jibel: we need to get that silo built correctly first then we can publish the deb and click15:58
bfillerKaleo filed a bug on it already https://bugs.launchpad.net/ubuntu/+source/python-flake8/+bug/150939615:59
ubot5Launchpad bug 1509396 in python-flake8 (Ubuntu) "Missing dependency on python-setuptools" [High,New]15:59
jibelKaleo, bfiller it's fine on stable too16:17
=== alan_g is now known as alan_g|EOW
dobeytrainguards: is it possible to land in xenial via train yet?17:11
sil2100dobey: yes17:11
dobeyawesome17:12
jgdxbarry, hey, what's the plan for ota versioning from s-i's end?18:18
barryjgdx: from client's end, nothing once 3.0.2 lands.  everything needed is already supported there.  sil2100 was working on server support iirc18:19
sil2100Yes, it's in the works now18:20
jgdxbarry, what are the eta for the former?18:20
jgdxis18:20
sil2100I would say I should be done by feature freeze18:20
jgdxsil2100, really. Okay18:20
sil2100Monday I hope to give barry something to review18:20
barryawesome18:21
jgdxcould we share a silo?18:21
barryi think it's waiting for qa sign-off.  rvr was doing qa18:21
jgdxokay, great18:21
jgdxI'll make one now then18:22
rvrbarry: I approved silo 23 yesterday18:22
barryrvr: rock on!  i was just going to ask since i didn't see it on requests18:22
barryrvr: is there anything more you need from me for that?18:22
rvrQA Signoff StatusQA Granted18:22
rvrStatusLanded18:22
rvrbarry: Seems done18:22
barry\o/18:23
barrythanks18:23
sil2100Yeah, saw it in the vivid-overlay changes18:23
jgdxsil2100, do you know anything re: the pep8 situation? Any change?18:23
sil2100jgdx: packages still in -proposed18:24
sil2100jgdx: I saw some autopkgtest regressions, but those should be resolved soon with a new upload of pyflakes18:25
sil2100jgdx: all caused by some package renames18:25
jgdxsil2100, okay, will it be resolved before tuesday?18:25
sil2100I'm sure it would, if not we'll consider giving a bit more time for landers that were blocked because of that18:26
bfillerjgdx: silo 39 has built now18:26
jgdxbfiller, great18:27
bfillerjgdx: that issue was resolved apparently18:27
jgdxhuh okay18:27
bfillerseb128 told me doko fixed it18:27
bfillerrvr: how's silo 11 testing coming?18:27
rvrbfiller: Hope to finish soon18:29
jgdxsil2100, could you given an example of what the tag key would contain as value?18:34
jgdxsil2100, re: ota18:34
sil2100jgdx: it will append something like this to the version_detail - "tag=OTA-6", so e.g. "version_detail": "ubuntu=20151015,device=20150911,custom=mako-1.1,version=26,tag=OTA-6"18:35
jgdxsil2100, +118:35
sil2100jgdx: I can't guarantee the ordering though, so don't take that for granted of course18:36
jgdxsil2100, sure thing.18:37
boiko_rvr: how is silo 11 going?18:38
=== boiko_ is now known as boiko
rvrboiko: I'm checking an issue with the messages scope18:44
rvrI've received some messages and the scope is blank18:45
boikorvr: ah yes, those are not really landing together with the silo, so, bugs in there should not block the landing really, I still have to fix a couple issues bfiller found in the new scopes implementation18:46
rvrboiko: I see18:46
=== fginther` is now known as fginther
rvrboiko: bfiller: Approving silo 1119:09
boikorvr: great! thanks!19:10
bfillerrvr: ty19:12
bfillerkenvandine: mind publishing silo 11?19:12
kenvandinesure19:14
kenvandinebfiller, that's alot of branches :)19:15
kenvandinebfiller, so that's set to "dual"19:15
kenvandineand built for wily and vivid19:15
bfillerkenvandine: crap19:16
bfillerso what does that mean?19:16
kenvandinealready qa granted19:16
kenvandinei can do the same thing i did last night19:16
bfillerkenvandine: sorry19:17
bfillerkenvandine: silo has been around for a long time :)19:18
rvrkenvandine: Silo 39 is targeted for xenial+vivid19:22
kenvandinervr, i'm doing 1119:22
kenvandinewhat's wrong with 39?19:22
rvrkenvandine: Shouldn't it land directly, or it is incorrectly targeted?19:22
rvrkenvandine: https://requests.ci-train.ubuntu.com/#/ticket/54619:23
kenvandineit should be xenial+vivid19:23
rvrkenvandine: Does it mean dual land?19:23
kenvandineyes19:23
rvrAh, I see, thanks19:23
kenvandinewe don't land for wily anymore19:23
kenvandinenp19:23
jgdxbarry, 3.0.2 is deprecating or removing Info altogether?19:48
=== chihchun is now known as chihchun_afk
barryjgdx: silently deprecated :)20:05
jgdxbarry, :))) very good20:06
alexabreurobru, ping20:17
robrualexabreu: pong20:25
alexabreurobru, sorry again on that copyright issue w/ jenkins, this is insane, ... I added the headers but ... https://jenkins.qa.ubuntu.com/job/unity-js-scopes-wily-amd64-ci/37/console20:26
alexabreurobru, I am at a loss20:26
alexabreurobru, the copyright seems fine http://bazaar.launchpad.net/~abreu-alexandre/unity-js-scopes/doc/view/head:/debian/copyright20:26
alexabreurobru, & the targetted files have headers e.g. http://bazaar.launchpad.net/~abreu-alexandre/unity-js-scopes/doc/view/head:/doc/docbuild/api.js20:27
alexabreuI must be missing something20:27
robrualexabreu: that's a different error though isn't it?20:28
robrualexabreu: didn't it say before it couldn't find the license? seems like now it says the license is not an acceptable license.20:28
alexabreurobru, yes, I progressed20:29
alexabreufrom unknown to this20:29
alexabreuso it picks it up20:29
robrualexabreu: as I said I'm not familiar with this copyright checker you're using here. I'm not sure who would know more about this.20:30
alexabreuok20:31
robrualexabreu: maybe ask slangasek20:32
ChrisTownsendtrainguards: May I have a silo assigned for https://requests.ci-train.ubuntu.com/#/ticket/561 please?20:33
robruChrisTownsend: you have the ability to assign your own these days20:34
ChrisTownsendrobru: Oh wow, I did not know that (obviously):)20:34
ChrisTownsendrobru: Thanks20:34
robruChrisTownsend: you're welcome. feel free to ask for help if something goes wrong but it should be pretty smooth20:34
ChrisTownsendrobru: Thanks again20:35
robruyou're welcome again20:35
ChrisTownsendrobru: I assume we do not have the ability to publish though, right?20:37
alexabreualexabreu, any idea (see my comments above) ^20:38
robruChrisTownsend: you can publish as long as there's no changes under debian/ and all your packages are prepared by merges (you can't publish manual sources)20:38
ChrisTownsendrobru: Ok.  If there are changes in debian/ do we ping a trainguard or is it queued up for review?20:39
robruChrisTownsend: you'd have to ping either a core dev or a MOTU depending on if your package is in main or universe.20:40
ChrisTownsendrobru: Ok, thanks for the lessons:)20:40
robruChrisTownsend: you're welcome20:40
slangasekrobru, alexabreu: sorry, I don't know anything about this license checker either.  But it appears to be getting called as part of pbuilder itself?21:20
slangasek/var/cache/pbuilder/build//24503/tmp/hooks/A10checklicenseheaders doesn't look like a package build directory21:20
robruslangasek: yes it does? build/nnnn21:27
slangasekreally?  that's a strange convention21:27
robruslangasek: i think that's a cowbuilderism21:28
slangasekI rest my case21:28
robruslangasek: alexabreu no wait, that log is from s-jenkins, not train Jenkins21:29
robruI officially have no idea what's going on there21:29
robrualexabreu: you should really poke cihelp for this21:30
fgintheralexabreu, looking21:32
robrufginther: thanks21:33
robruslangasek: actually though I thought you might be more knowledgable about policy, eg, is there some reason that "BSD 3 clause" wouldn't be acceptable in ubuntu or something.21:39
slangasekrobru: no, that's perfectly acceptable in Ubuntu, but it's possible this is a license checker that tries to verify that debian/copyright matches the source21:39
robruslangasek: k, I dunno then. the headers and the debian/copyright appear to match to me21:40
robruthanks21:40
* robru --> lunch21:41
fgintherrobru, this is just a case of using an overly restrictive license check. There's nothing really wrong with the files21:47
fgintherrobru, in case you were curious21:47
fgintheralexabreu, should be fixed now, and your MP is being re-run.22:11
robrufginther: haha, thanks. where's the documentation on that license checker?22:16
=== salem_ is now known as _salem

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!