=== bladernr_ is now known as bladernr_afk [07:19] good morning [07:20] slangasek: vmware packages> yes, except for the missing license and wrong debian/copyright, but as I said this might be a point where we have usually ignored any blatant error anyway [08:01] Anyone know why http://reports.qa.ubuntu.com/reports/kernel-bugs/reports/rls-p-tracking-bugs.html seems to be stuck? [08:01] Last generated on Thursday. [08:44] 1.1.0-19ubuntu1.1~ppa1 [08:44] oops [08:50] cjwatson: last time I asked apw about it, and between him and bjf they poked it to update; they didn't tell me teh details what went wrong, though [08:51] they mentioned something about "LP upgrade", not sure if their cronjob needs manual handholding if it fails once [08:55] could a archive admin please check/accept my vmware-view-client upload to lucid? [09:02] mvo: looking [09:05] mvo: so, debian/copyright still smells fishy (including open source components without providing their source, etc.), but as we discussed by mail I'll just ignore this :) [09:05] so, accepted [09:14] pitti: thanks! more to come soon (maverick, natty :) [09:52] vmware-view-client for maverick, natty is now up as well, lucid appears to be build and may need a binary-new, not sure though, the LP page looks a bit odd [10:49] mvo: lucid bin-NEWed [10:49] mvo: sorry, didn't see your ping earlier [10:49] * pitti just spent about an hour writing the stable+1 summary/handoff [10:50] mvo: m/n source-NEWed, too; will watch the queues for binNEW [10:53] thanks pitti! much appreciated === iulian is now known as Guest55423 [10:57] mvo: both built and binNEWed [10:58] mvo: if someone could verify the app-install-data-partner SRUs, I can move them to -updates as well [10:58] pitti: great, I will ask in ubuntu-testing [11:08] mvo: you can also test it yourself if you have time and VMs/chroots [11:09] pitti: oh, even better. I shyed away from it because I did the SRU upload [11:09] mvo: *shrug* I trust you to use the actual .debs from -proposed :) [11:09] aside from that, it's just verifying that they show up in s-c and install correctly, right? [11:09] yeah [11:09] so for lucid/maverick etc. you might still need to wait for the publisher [11:10] ok [11:11] mvo: I'll now do some vacation-y stuff now (xmas prep, etc.), but will check IRC from time to time [11:12] pitti: thanks, *much* appreciated [11:12] kein Problem :) [13:45] pitti: all sru verification done [13:45] mvo: saw in the bug, moved to -updates five mins ago :) [13:45] !! [13:45] * mvo hugs pitti [13:45] * pitti hugs mvo, thanks for your hard work on this === doko_ is now known as doko === Guest55423 is now known as iulian === bladernr_afk is now known as bladernr_ [17:14] https://jenkins.qa.ubuntu.com/view/Precise%20ISO%20Testing%20Dashboard/view/Daily/ - why do some of the jobs show up with rain clouds when there's "100%" for the success column? [17:16] slangasek: isn't it related to the number of failures over the last x runs or x days? Jenkins doesn't seem reachable here at the moment but I seem to remember reading something like that [17:16] I don't know what it's related to :) [17:16] it's confusing, that's why I ask :) [17:17] * slangasek wonders when armhf should be moved from http://people.canonical.com/~ubuntu-archive/testing-ports/precise_probs.html to http://people.canonical.com/~ubuntu-archive/testing/precise_probs.html [17:17] maybe only after LibO is built ;) [17:19] slangasek: hover says "1 out of the last 5 builds failed" [17:19] so the "100%" only refers to the number of successes in the current build? [17:20] right [17:20] ok [17:21] but yeah, I agree that showing 100% everywhere and having an icon indicating some kind of failure is a bit confusing ;) === cjwatson_ is now known as cjwatson