[07:23] <mardy> trainguards: how can I prevent jenkins from generating a new changelog, and therefore avoid this error: https://ci-train.ubuntu.com/job/ubuntu-landing-001-1-build/206/console ?
[07:28] <robru> mardy: your packaging isn't really conforming to train expectations
[07:29] <mardy> robru: apparmor-easyprof-ubuntu is not developed by us, I don't think I should change the packaging format
[07:29] <robru> mardy: then i guess you can't really release it in the train. Use a manual source package instead of mp.
[07:30] <mardy> robru: or I guess I can modify the packaging format just for the train, and once the testing goes fine, we revert those packaging changes and land it as usual
[07:31] <robru> mardy: that sounds like a massive hassle, why bother? Just manually build a package and upload to the silo
[07:31] <mardy> robru: ah, I didn't know that this could be done. Just by using dput, or how?
[07:32] <robru> mardy: yeah just make sure you're in the right team, or sil2100 can do it for you
[07:34] <robru> mardy: easiest might be to upload to a ppa you control, since i don't think you're in the team. sil2100 can copy it shortly (I'm literally in bed)
[07:55] <abeato> sil2100, mind assigning a silo for line 73?
[08:01] <sil2100> abeato: sure
[08:01] <abeato> sil2100, thks
[08:01] <sil2100> mardy: provide me with a package in a PPA or a source package and I'll upload :)
[08:02] <sil2100> mardy: https://wiki.ubuntu.com/citrain/LandingProcess#CI_Train_for_manual_source_uploads
[08:03] <sil2100> jibel, davmor2, popey: anything to discuss, or we can skip?
[08:08] <jibel> sil2100, nothing really important and the flow of incoming silos dropped
[08:10] <davmor2> sil2100: Loads to discuss....most about how cute your cat is....but not really work related not from last night anyway
[08:10] <popey> hah
[08:13] <sil2100> The cat is indeed cute, just that my girlfriend gets tired of him biting her feet in the morning
[08:13] <sil2100> In the bed
[08:14] <sil2100> It's his way of saying: "I miss you mommy, get up and play with me"
[08:19] <popey> ours used to do that
[08:19] <popey> they now get locked in the kitchen at night
[08:21] <sil2100> We usually throw him out of the bedroom when he does that too much and lock the door, still didn't learn how to use the door handle
[08:22] <sil2100> But I hope he'll just mature away from biting at night
[08:22] <sil2100> ;)
[08:25] <davmor2> sil2100: does mean there is no meeting then
[08:29] <sil2100> davmor2: yep
[08:29] <davmor2> sil2100: you have to post pictures of your cat then :P
[08:46] <popey> jibel: davmor2 got a new Reminders/Notes app for testing. Will anyone have some time to test today?
[08:47] <sil2100> Seeing the number of silos coming up, sure
[08:49] <davmor2> popey: possibly fill it in
[08:51] <jibel> popey, sure, sil2100 is kindly proposing to do it himself :)
[08:52] <sil2100> ...scratch that! Seeing the number of silos coming up, no way
[08:54] <sil2100> ;)
[08:54] <mandel> sil2100, what does " is in the Proposed pocket" mean?
[08:55] <mandel> sil2100, also, does the packages from silo 09 sync with silo 17?
[08:55] <sil2100> mandel: it means the package is in wily-proposed
[08:55] <mandel> sil2100,  ok, great
[08:55] <mandel> sil2100, so, I'm wondering, the packages in silo 09, are they going to land in wily and then can they be sync to silo 17?
[08:55] <sil2100> mandel: if all is ok with the packages those should migrate to the release pocket soon
[08:55] <mandel> sil2100, sorry for the mess, trying to get this landed :-/
[08:56] <mandel> sil2100, ok, great
[08:56] <sil2100> Yeah, we can sync them then if needed :) Let's see what the excuses page tells us
[08:57] <sil2100> mandel: ok, I see an autopkgtest failed for u-d-m
[08:57] <mandel> sil2100, oh, can I see the error?
[08:57] <sil2100> Although it's hm, 'informational'
[08:57] <sil2100> Not sure what that means, maybe this autopkgtest doesn't block it
[08:58] <mandel> sil2100, where can I see that error? I should be able to judge :)
[08:58] <mandel> or maybe not hehe
[08:58] <sil2100> http://autopkgtest.ubuntu.com/packages/s/system-image/wily/amd64/ <- autopkgtest for system-image as ran because of u-d-m
[08:59] <mandel> sil2100, thx
[08:59] <sil2100> It's a cloud autopkgtest, first time I see those
[08:59] <sil2100> mandel: anyway, one autopkgtest is still running
[08:59] <sil2100> We'll see if it migrates once it's done
[09:00] <mandel> sil2100, I'm looking at the test anyway
[09:01] <jibel> sil2100, the cloud version is just informal and not blocking promotion IFAIK. The non-cloud version is there https://jenkins.qa.ubuntu.com/job/wily-adt-system-image/lastBuild/
[09:02] <sil2100> jibel: so as I expected, that's why I thought it probably doesn't block
[09:02] <jibel> informational*
[09:03] <sil2100> Thanks for clearing it out ;)
[09:30] <jamesh> jibel: is there anything further that needs to happen before the thumbnailer can get out of proposed limbo?
[09:32] <popey> jibel: added reminders/notes to the sheet, ready for testing thanks.
[09:40] <sil2100> popey: assigned in the sheet, QA should get it on the queue in a moment
[09:46] <jibel> jamesh, everything looks good on excuses.
[09:46] <jibel> infinity, do you know why thumbnailer is a valid candidate and doesn't get out of proposed?
[09:50] <sil2100> jibel: looks like ubuntu-touch is uninstallable then... maybe the seeds need to be updated so that the removed library isn't pulled in?
[09:50] <sil2100> jibel: checking that now, but this might be the cause
[09:52] <popey> ta
[09:54] <jamesh> sil2100: ubuntu-touch depends on thumbnailer-service, and there are deps on the QML plugin.  I don't see any dependencies on libthumbnailer0 (the removed package) outside of other binary packages provided by thumbnailer
[09:56] <sil2100> jamesh: same here, don't see anything in the dependencies, let me take a closer look
[09:57] <dbarth__> hey
[09:58] <dbarth__> for silo 31, i would like the silo to become wily only, as it's desktop oriented, and is really planned for 15.10
[09:58] <sil2100> dbarth__: ok, will convert it in a moment
[09:58] <dbarth__> super, thank you sil2100
[09:59] <dbarth__> the silo has been tested, so we can then mark ok and land on wily only
[09:59] <dbarth__> sil2100: while we're at it, i think we could free silo 1, per robru's recommendation, and i will migrate to a ppa for the time being
[10:00] <dbarth__> and sort out the debian packaging there
[10:01] <sil2100> Yyyyh
[10:01] <sil2100> dbarth__: ok, makes sense, the earlier Yyyyh was to the issue I'm investigating now ;)
[10:01] <sil2100> jamesh, jibel: I think I have it
[10:03] <sil2100> eh
[10:04] <sil2100> I thought we fixed that with Mirv...
[10:05] <sil2100> jamesh, jibel: I'll try to unblock it in a moment, need to check the logs first
[10:06] <sil2100> Ah! I know what happened, we fixed that on vivid-overlay
[10:06] <sil2100> Didn't do the same fix for wily
[10:06] <sil2100> Ok, makes sense, fixing
[10:07] <dbarth__> can you help me get armhf builds enabled on that new ppa though: https://launchpad.net/~webapps/+archive/ubuntu/new
[10:07] <dbarth__> i'll move the branches over there
[10:07] <dbarth__> sil2100: ^^
[10:07] <sil2100> dbarth__: hey! I think we'd need someone like infinity and slangasek for that
[10:07] <sil2100> infinity, slangasek: ^
[10:11] <sil2100> dbarth__: silo 31 reconfigured, vivid package removed, please run a WATCH_ONLY build :)
[10:13] <dbarth__> sil2100: ok
[10:14] <dbarth__> https://ci-train.ubuntu.com/job/ubuntu-landing-031-1-build/13/console
[10:15] <sil2100> dbarth__: ok, it's ready now :)
[10:24] <jamesh> sil2100: so what was holding it up?
[10:26] <sil2100> jamesh: qtdeclarative-opensource-src-gles... thumbnailer depends on latest ubuntu version symbols, so the -gles version needs to have the exact same version
[10:26] <sil2100> And it didn't, as the -gles and main version never had to follow the same versioning
[10:26] <sil2100> (mostly because the -gles packages are ubuntu-specific, where normal ones have debian revisions)
[10:27] <sil2100> So I had to bump qtdeclarative-opensource-src-gles from 5.4.2-0ubuntu3 to 5.4.2-1ubuntu3
[10:27] <sil2100> So, in fact, we're now lying that this package had a debian releaase somewhere ;p But uh, no other way of resolving that without a lot of effort
[10:28] <sil2100> Building the package right now, I'll test it once it builds and publish
[10:57] <anpok> ping trainguards
[10:57] <anpok> we need an update of the packages in silo 053
[10:57] <anpok> with the packages that landed from the mir 004 yesterday
[11:00] <sil2100> anpok: hm, did those migrate to the release pocket in the end? Did the boottest get whitelisted?
[11:01] <anpok> sil2100: yes, and fginther looked into improving the boottest to also enforce driver upgrades
[11:01] <anpok> sil2100: note.. silo004 contained a new mir package, than the one that got migrated from proposed to wily
[11:02] <anpok> *newer
[11:03] <sil2100> anpok: hmmm
[11:03] <sil2100> anpok: ok
[11:03] <anpok> yes big hmm
[11:03] <anpok> i made a fix attempt yesterday, that failed, reverted it...
[11:03] <sil2100> anpok: so basically you'd like to have all the packages that landed in the archive yesterday in silo 53, right?
[11:04] <anpok> all but gtk+3.16 but that didnt land since it was already outdated afaik. So, yes.
[11:04] <sil2100> gtk+3.16 doesn't make sense in the overlay anyway, so I'll remove it from the package-list
[11:05] <anpok> i think someone else already made a gtk+3.14 in vivid+o anyhow
[11:05] <anpok> so yes I think it is not necessary
[11:05] <sil2100> I'll reconfigure the silo to be a sync silo, and those packages that cannot be synced I'll manually upload
[11:05] <sil2100> Give me a few minutes to finish up what I was doing tho ;)
[11:06] <anpok> thank you!
[11:08] <sil2100> jamesh: publishing the fix, we should be unblocked soon
[11:08] <jamesh> sil2100: yay!  Thanks for your help
[11:08] <sil2100> yw!
[11:10] <sil2100> anpok: on your request now
[11:14] <sil2100> uh, symbols file removal
[11:15] <sil2100> I can't publish that sadly
[11:15] <sil2100> Not without some other automated way of checking for abi-compliance
[11:16] <sil2100> jamesh, marcustomlinson: are you guys using something like dh-acc or abi-compliance-checker in an automated way in unity-scopes-api ?
[11:18] <Laney> Symbols files are also used to give reverse dependencies the right versions
[11:18] <marcustomlinson> sil2100: no we're not. tvoss ^, any suggestions?
[11:18] <Laney> Those other thing don't fully replace them
[11:19] <sil2100> Laney: indeed, you're right
[11:19] <sil2100> anpok: hey, is there a specific build-order required in the mir silo?
[11:29] <marcustomlinson> sil2100: ok, putting symbols files back sadly
[11:38] <doko> sil2100, you really need to update qtdeclarative-opensource-src-gles - 5.4.2-0ubuntu5 (Newer version available) in silo 16
[11:40] <sil2100> doko: ok, I'll update the one in the PPA, since the package I pushed to the archive is just a version bump
[11:40] <sil2100> So I'll do a similar bump in the transition PPA
[11:40] <sil2100> doko: thanks for mentioning
[11:42] <doko> sil2100, sure, use the next version number then
[11:46] <sil2100> doko: pushed corrected, should be ok once it builds
[11:57]  * sil2100 goes off to prepare lunch
[12:33] <anpok> sil2100: well we usually first have to build mir then the rest.. then -gles sync packages. But do you need that info for a sync silo?
[12:35] <jdstrand> mardy: how we do it is in the spreadsheet, add apparmor-easyprof-ubuntu to the 'Additional source packages to land' column, then dput directly to the silo ppa or pocket copy it into the silo ppa from another ppa
[12:36] <jdstrand> mardy: you can still do MPs for other stuff
[12:36] <jdstrand> mardy: in the same silo
[12:36] <mardy> jdstrand: OK, thanks, but after talking with dbarth we convened that it's better to use a PPA, not to block one silo for long (we might be testing this for quite some time)
[12:37] <jdstrand> mardy: ok. let me know if you need help with a silo at some future date
[12:45] <doko> sil2100, please could you fix the silo 16 and not leave it in a broken state?
[12:49] <mandel> sil2100, what is going on with silo 09? Just trying to understand :-/
[13:34] <anpok> sil2100: problems in silo 53?
[13:36] <sil2100> anpok: hm, just got from lunch, let me take a look at that - it looks as if the upload got rejected
[13:38] <anpok> ok, also the merge of the mps from silo004 hasnt happened yet (afaik) - or will that happen later and separately
[13:38] <anpok> sil2100: I am off for about two hours now.. will be back..
[14:17] <seb128> did anyone else notice bug #1478022 ?
[14:18] <seb128> click details take like 10 seconds before to render any content here
[14:21] <jibel> seb128, it takes around 5s here. Is it specific to an app or you tried different ones?
[14:21] <seb128> jibel, I tried different ones
[14:21] <seb128> calendar, dekko
[14:21] <jibel> I tried the same
[14:22] <jibel> scrolling is really broken when it's loading though
[14:23] <jibel> when scrolling is slow dash uses 100% cpu
[14:25] <seb128> jibel, I reported https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1478022 as well
[14:25] <seb128> and https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1478026
[14:26] <seb128> those feel like regressions
[14:26] <seb128> I wonder if that's the same class of issues than bug #1476282
[14:27] <seb128> pmcgowan, ^ unsure if others reported issues around those lines? we should also probably have that today's bug on the ota6 list, seems quite some users hit the "missing day info" issue
[14:29] <abeato> sil2100, could you publish silo 8 ? I am not sure whether I can do that or not
[14:30] <sil2100> abeato: on it, I have a meeting right now tho'
[14:30] <abeato> sil2100, nw, not in a hurry
[14:31] <pmcgowan> seb128, yes kyle has been trying to reproduce it etc
[14:34] <seb128> pmcgowan, I get it pretty easily, but I've other issues with other scopes cf the click preview ones I just listed, I wonder if there are some issues in the scope framework recent updates
[14:39] <sil2100> abeato: ^ could you approve some of the merges?
[14:40] <abeato> sil2100, working on that
[15:00] <bfiller> sil2100: can we get Elleo (michael-sheldon) added for permissions for the ci-train spreadsheet, etc so he can create silos and build?
[15:01] <sil2100> bfiller: sure thing! I thought he had permissions already actually
[15:01] <sil2100> Let me add him
[15:01] <bfiller> sil2100: oh, maybe he does
[15:02] <sil2100> bfiller: hm, he wasn't, I was sure he was... anyway, added now
[15:23] <sil2100> kgunn: I'm re-assigning silo 53 to another silo
[15:24] <sil2100> Since we seem to have some issues with source synces
[15:26] <kgunn> @vogons ^
[15:45] <abeato> sil2100, could you try now publishing silo 8 ?
[15:47] <Laney> too late
[15:47] <Laney> I have all the power so did it
[15:47] <abeato> :)
[16:27] <infinity> jibel: What triggers the DKMS jenkins jobs?
[16:29]  * jibel tries to remember the details
[16:30] <davmor2> infinity: the words jibel is looking for is Magic
[16:30] <jibel> infinity, there a a daily job that verifies if there is a new dkms module or kernel in one of the target release/pocket or ppa
[16:30] <infinity> jibel: Okay, so I just need to be patient for that cronjob?
[16:31] <infinity> jibel: I tried triggering one by hand from the jenkins UI, and that seemed to do nothing. :P
[16:31] <infinity> Oh, but maybe that was because it was wily-release, and it's outsmarting me.
[16:31] <infinity> But there is no wily-proposed job, so I guess I wait.
[16:31] <jibel> infinity, I noticed that the node they were running on died 10h ago, cihelp restarted it, but these jobs all failed and won't be restarted automatically
[16:32] <jibel> infinity, if should do something :)
[16:32] <jibel> it*
[16:32] <jibel> infinity, which one was it?
[16:32] <infinity> jibel: Well, this is the one I retried: http://d-jenkins.ubuntu-ci:8080/job/dkms-wily-release_canonical_kernel_team_ppa-generic-fglrx_core/
[16:32] <infinity> jibel: But the dkms package I'm wanting to verify fixed is in -proposed, not release, maybe it checks for versions changes in the release pocket and bails out of nothing's new?
[16:33] <jibel> interesting: /tmp/hudson2415302381661435058.sh: 11: cd: can't cd to /home/auto-package-testing/dkms-testing/
[16:33] <jibel> infinity, in this case ^ it a real problem
[16:34] <infinity> Oh, fun.  Then consider the problem reported!
[16:34] <infinity> jibel: HEY JIBEL.  THERE'S A PROBLEM.
[16:34]  * jibel -> EOW
[16:34] <infinity> Hahaha.
[16:34]  * infinity mails cheese and wine.
[16:34] <infinity> That's what fuels French people, right?
[16:34]  * infinity throws in a baguette for good measure.
[16:39] <mandel> trainguards how do I bump the version number from 0.9 to 1? Is there some magic to make the bot do it?
[16:39] <sil2100> mandel: hey!
[16:39] <mandel> sil2100, though you were done for the day :)
[16:40] <mandel> sil2100, so the so is 1 gut the ppa creates 0.9-foo-bar
[16:40] <sil2100> mandel: just modify the debian/changelog of the package with a merge request in the train and add a new changelog entry with the new upstream version
[16:40] <sil2100> So, an example:
[16:40] <mandel> dch -i and the Bump version number due to blah blah :wq
[16:40] <mandel> sil2100, ^
[16:41] <sil2100> Let's say you have merges for project foo and the last changelog entry is 0.9+15.04.20150707-0ubuntu1
[16:41] <sil2100> And you want to change to 1.0
[16:41] <sil2100> THen you do dch -i, change the latest version number to 1.0 (or 1.0-0ubuntu1, doesn't matter) and get that through the train
[16:41] <sil2100> The CI Train will parse that and convert it to a CI Train number itself
[16:42] <sil2100> Just be sure to leave it as UNRELEASED
[16:42] <mandel> ack
[16:53] <slangasek> sil2100: do you know if dbarth is specifically looking for https://launchpad.net/~webapps/+archive/ubuntu/new to be a devirt ppa, or just have armhf enabled?
[16:56] <sil2100> slangasek: hm, not sure, I think he might want to poke us later to perform binary syncs after testing is done, but I suppose we can do source-copies instead before release
[16:56] <sil2100> We'd need him to get to know his rationale
[16:56] <slangasek> sil2100: why would he be asking for binary syncs from here instead of using the silos?
[16:57] <infinity> sil2100: If there was to be binary copying, it would need to be devirt, with all arches on, and the right configs to match.  And Canonical-only, etc.
[16:57] <slangasek> (in other words: I don't think we would want to allow that)
[16:57] <infinity> sil2100: But my impression from scrollback was just that he wanted somewhere to play without having to lock a silo.
[16:57] <sil2100> infinity: might be
[16:57] <infinity> And "play" doesn't imply "release versions".
[16:57] <sil2100> As I said, we can do source-copies to silo PPAs before release
[16:57] <slangasek> the main difference between a devirt and non-devirt ppa with armhf support is that non-devirt is emulated, and the emulation is sometimes buggy.
[16:58] <infinity> And s-l-o-w.
[17:08] <sil2100> popey: did you publish the new notes app?
[17:09] <popey> sil2100: not yet, will do shortly
[17:09] <sil2100> popey: ok, thanks :)
[17:11] <davmor2> sil2100: it only just passed
[17:12] <popey> :)
[17:20] <popey> sil2100: done
[17:20] <sil2100> popey: thanks! Yay :)
[18:22] <kenvandine> mandel, can silo 9 be published again?
[18:31] <anpok> sil2100: do you know when ci will merge the MPs of silo004?
[18:37] <kgunn> trainguards you can blow away silo 42, that's old/stale...do i just delete the cooresponding row in the sheet ??
[18:37] <kgunn> didn't want to inadvertently break somthing
[18:37] <robru> kgunn: yep you can delete rows no problem.
[18:39] <kgunn> anpok: it needs testing set to passed i think
[18:39] <kgunn> it says "no" in the sheet right now
[18:39] <robru> anpok: they get merged after they get published. silo says 'packages built'
[18:40] <anpok> hum
[18:41] <anpok> that info is gone again
[18:43] <kgunn> now they're ready
[18:43] <kgunn> anpok: are you going to have a beer or 2 this weekend after all this :D
[18:43] <anpok> kgunn: it isnt over yet!!!
[18:43] <kgunn> lol
[18:43] <kgunn> true
[18:44] <kgunn> anpok: if those land and migrate ok, i can start testing for vivid+o this afternoon....
[18:44] <robru> anpok: do you know anything about this gtk upload that happened without you? https://launchpad.net/ubuntu/+source/gtk+3.0/3.16.6-1ubuntu1
[18:45] <anpok> robru: yeah. there was a problem in the gtk+3.16 package .. and I believe seb fixed it and uploaded it independent from the silo
[18:45] <robru> anpok: ok I'll remove it from the silo then since we can't publish a lower version over the higher one in proposed
[18:45] <anpok> yes
[18:47] <anpok> robru: i would like to amend that mir0.14.0 was already released to wily
[18:47] <robru> anpok: ok?
[18:47] <anpok> not sure what happened to the row state
[18:47] <robru> anpok: the silo has packages that are newly build and not released yet to wily right?
[18:47] <anpok> es
[18:47] <anpok> yes
[19:10] <kyrofa> trainguards: Does the CI train support launchpad git the same as bzr?
[19:16] <robru> kyrofa: nope, not at all
[19:19] <kyrofa> robru, thanks for the info. Do you know if that's on the roadmap at all?
[19:20] <robru> kyrofa: in theory I suppose. lots of other priorities right now though. don't hold your breath, sorry
[19:20] <kyrofa> robru, alright, thanks!
[19:24] <robru> kyrofa: you're welcome
[19:44] <kgunn> anpok:  so do you need to "build" something ? seems like the gtk upload changed the status once again
[19:44] <kgunn> "ready to build"
[19:52] <anpok> kgunn: no clue whats going on
[19:53] <kgunn> robru: does anpok just need to do a rebuild of 1 pkg or something ? ^
[19:55] <robru> kgunn: anpok oh sorry guys, I was fiddling around with that and then got distracted
[19:55] <robru> kgunn: anpok: I had to reconfigure to remove gtk because the version in the silo is lower than the version in archive. will publish shortly
[19:57] <mandel> kenvandine, yes, sorry had to bump the version number
[19:58] <kenvandine> mandel, i pushed the button :)
[19:58] <mandel> kenvandine, no need to recompile the other packages, it was a simple chalog change
[19:58] <mandel> kenvandine, oh, hehe
[19:58] <mandel> kenvandine, sorry I had dinner (22:00) :)
[19:58] <kenvandine> no worries man
[19:58] <kenvandine> i figured you were gone so took care of it
[19:59] <mandel> kenvandine, awesome, thx
[19:59] <kenvandine> np
[20:06] <robru> kgunn: anpok: just want to confirm with you guys that the only packages that changed since last publisher are xorg and mir?
[20:06] <anpok> xorg changed?
[20:09] <kgunn> anpok: robru that wouldn't be completely shocking...silo 4 has been around 4 weeks, robert ancell and co prolly took in a new version of xorg
[20:12] <robru> kgunn: anpok: the new xorg is from the 15th, and appears not to be in wily yet.
[20:13] <robru> kgunn: anpok: ok for some reason the train is still failing to recognize that glmark is in the archive already, so if you happen to notice mir and xorg migrate (eg, the status will only say "glmark is in the silo" and won't mention any other packages), ping me and I can make the merge happen.
[20:34] <robru> jamesh: does silo 30 not need qa?
[20:55] <kgunn> robru: yo, silo stuck on glmark2 now
[21:49] <robru> kgunn: anpok: https://ci-train.ubuntu.com/job/ubuntu-landing-004-3-merge-clean/27/console lol, 16 builds of mir in total