[02:40] <troy_s> kwwii: Yikes
[02:40] <troy_s> kwwii: You are using Hardy apparently -- bzr no workie on the pull down!
[02:48] <troy_s> kwwii: if you can figure out how to resolve it, let me know.   I wouldnt leave it open though.
[02:54] <troy_s> _MMA_: Yet more reasons to love FOSS -- you learn things daily.  Always knew about backports, never really pulled them I guess.
[02:54] <troy_s> _MMA_: Breaks stuffs?
[02:56] <_MMA_> Well, for me, if F'ed a new BZR branch I did. Now like you, everyone needs to use the backported BZR to upload to my branch.
[02:56] <_MMA_> s/if/it
[02:56] <_MMA_> But yeah. Best to grab what you need only.
[04:13] <troy_s> _MMA_: What do you think of the Fela Kuti wallpaper?
[04:13] <troy_s> _MMA_: It's pretty bloody well crafted.
[04:15] <_MMA_> Yeah. I grabbed it. Im using Who's on all my desktops now though. :P Just something about it.
[17:12] <kwwii> I just added a search icon to https://code.launchpad.net/~kwwii/human-panel-icons/trunk
[20:51] <troy_s> kwwii: Grr.
[20:51] <troy_s> kwwii: I wonder if I pull the branch using the newer bzr and revert to the older one if that would fix the issue
[20:52] <troy_s> kwwii: Or if it will be boned after you pull the original bzr version then push using the newer one.
[20:52] <_MMA_> No. It depends on what version was used to create the branch.
[20:52] <troy_s> kwwii: Also, the directionality of the wave emissions is very close to the sound icon.  I was going to try and make a blob emanating from the center with a more circular full set for wifi.
[20:53] <_MMA_> You would have to pull the info, nuke the branch and re-up it with the old bzr version.
[20:53] <troy_s> _MMA_: So if I pull a branch using the new version, revert my bzr, destroy the .bzr and re-push a branch
[20:53] <troy_s> _MMA_: I think that might work.
[20:53] <troy_s> (as in a full bzr init, bzr add, bzr commit, bzr push)
[20:53] <_MMA_> It should.
[20:53] <_MMA_> (so I was told)
[20:59] <kwwii> wow, what is the issue?
[20:59] <kwwii> sounds pretty devastating
[21:00] <kwwii> troy_s: yeah, I was thinking that the waves are too much alike
[21:00] <_MMA_> kwwii: Your initial branch of the icons were done with a version of BZR incompatiable on some levels with the current release version of bzr found in Gutsy.
[21:01] <kwwii> _MMA_: hrm, I am running gutsy
[21:01] <_MMA_> Then you did like I did and grabbed a update from backports.
[21:01] <_MMA_> Look at the version of bzr you're running.
[21:02] <kwwii> Bazaar (bzr) 1.0.0
[21:02] <_MMA_> kwwii: Do: bzr version
[21:02] <_MMA_> Yep. You grabbed the backport update.
[21:03] <kwwii> freaky, I did not know that there was an issue with which version of bzr you had
[21:04] <troy_s> kwwii: You must have bumped up bzr.
[21:04] <troy_s> kwwii: If you are running gutsy
[21:04] <troy_s> kwwii: Remove backports from the list and do a full remove / purge of bzr
[21:04] <troy_s> kwwii: Then re-add it with backports disabled.
[21:05] <troy_s> kwwii: It is sort of what I was getting at -- pull the branch as it is now current -- revert my bzr, strip the .bzr dir out, re-initialize and commit the new branch.
[21:05] <troy_s> kwwii: But that would mean that you would need to continue work on the .90 implemented branch.
[21:06] <troy_s> kwwii: Nice to see the asstastic power button icon is getting into trouble (as it should have been canned ages ago -- your icon is about as good as I have seen yet)
[21:06] <kwwii> what is default in hardy?
[21:06] <kwwii> hehe, thanks
[21:06] <kwwii> feel free to make any improvements you feel necessary, btrw
[21:06] <kwwii> btw
[21:07] <_MMA_> 1.0 is in hardy.
[21:07] <_MMA_> Messed up thing for me is they didnt backport everything.
[21:07] <_MMA_> Like bzr-buildpackage.
[21:08] <troy_s> kwwii: I'd like to get going on some... first... I think we need to resolve the bzr issue.
[21:08] <troy_s> kwwii: Any chance you can revert your bzr so as to not cause issues on your end?
[21:09] <troy_s> kwwii: If yes... I'll get an updated branch and fix it all.
[21:09] <troy_s> kwwii: But first a shower.  Gotta love force majure.
[21:12] <troy_s> Nice stuff here for those of a certain mindset... http://www.divinecaroline.com/article/37963/43588
[21:21] <kwwii> ok, so now I am at Bazaar (bzr) 0.90.0
[21:21] <kwwii> how do I get rid of the old stuff on launchpad?
[21:22] <_MMA_> kwwii: As long as your data on you machine you can kill the .bzr folder in that folder.
[21:22] <_MMA_> Im unsure how to kill the branch. Troy knows.
[21:22] <kwwii> _MMA_: I did a re-init of the dir after removing the .bzr dir
[21:22] <_MMA_> ok
[21:22] <kwwii> all I need to do is to push the new trunk in place of the old one
[21:23] <_MMA_> Sayz you. Ok. :)
[21:23]  * _MMA_ has no experience actually doing it.
[21:25] <troy_s> kwwii: The best thing I can think of is just that
[21:25] <troy_s> kwwii: Just rm the .bzr, re-init, add, commit, push.
[21:25] <troy_s> kwwii: And change the 'trunk' focus to your new branch
[21:25] <troy_s> relatively easy or at least should be.
[21:26] <troy_s> (the last step being inside of launchpad)
[21:31] <kwwii> bzr: ERROR: Unknown branch format: 'Bazaar pack repository format 1 (needs bzr 0.92)\n'
[21:31] <maccam-desktop> kwwii: grr, i'm reading through the logs/the launchpad page, and i can't tell: is the new theme design definitely pushed back to Hardy+1?
[21:32] <kwwii> maccam-desktop: the raically new theme will come later, yes
[21:32] <kwwii> we are changing things
[21:33] <maccam-desktop> kwwii: ok. you should change the hardy-theme blueprint overview to make this clear, or make it deferred or something... i couldn't tell if the decision was official/final or not because of that
[21:34] <kwwii> troy_s: https://code.launchpad.net/~kwwii/human-panel-icons/main
[21:34] <kwwii> I did change the blueprint irrc
[21:34] <kwwii> at least I think I did
[21:34] <kwwii> :-)
[21:35] <maccam-desktop> kwwii: https://blueprints.launchpad.net/ubuntu/+spec/hardy-theme
[21:37] <kwwii> yeah, I missed the overview part
[21:38] <kwwii> but I did change the text itself :p
[21:38] <kwwii> now it is changed
[21:38] <kwwii> troy_s: let me know if that branch works
[21:43] <_MMA_> kwwii: Who replied to you.
[21:43] <_MMA_> "Who" as in the artist. :P
[21:44] <kwwii> _MMA_: I know Who (you are talking about) :p
[21:44] <kwwii> I also replied back right at him
[21:44] <_MMA_> Ok. I just wanted to avoid a whole Abbott and Costello thing. :P
[21:46] <maccam-desktop> kwwii: by adding "This is the first step in that direction"? This is the theme spec for 8.04, not a general artwork spec :-\ I think it should say something like "The theme of Ubuntu 8.04 will be an improved version of the existing Human theme.   Repo works.
[22:39] <troy_s> kwwii: The colour icons are far surpassed by the monochromatic ones by a long shot.
[22:41] <kwwii> cool
[22:42] <kwwii> I think that the simplicity of them should make it easier for others to contribute
[22:44] <kwwii> I am off to bed, night all
[22:45] <_MMA_> night
[22:59] <troy_s> kwwii: Damn you
[22:59] <troy_s> kwwii: one second
[23:00] <troy_s> kwwii: 1) nuke the other branch now :)
[23:00] <troy_s> 2) give me a second... i added three.
[23:32] <somerville32> :)


[08:10] <lordievader> Good morning.
[08:32] <smartboyhw> Riddell, I'm asked to ask you to approve fcitx-qimpanel in NEW
[11:18] <BluesKaj> 'Morning folks
[11:30] <soee> hiho
[11:45] <Peace-> bye bye
[15:26]  * shadeslayer is sad
[15:26] <shadeslayer> http://paste.kde.org/p80d46cb7/ < QtWebkit still fails
[15:32] <Riddell> shadeslayer: a different failure?
[15:32] <shadeslayer> yeah
[15:34] <Riddell> shadeslayer: well looks like it needs a -lfoo added as it can't find some library or other
[15:34] <Riddell> ask upstream?
[15:35] <shadeslayer> probably not, I disabled 3D stuff
[15:36] <shadeslayer> and to me it seems that the code isn't properly ifdef'd
[15:36] <Riddell> wouldn't surprise me
[15:37] <shadeslayer> I think upstream is enjoying their weekend
[15:37] <shadeslayer> will ask tomorrow
[15:37] <Riddell> shadeslayer: I got the pandaboard in a stable setup if it's useful to have an account on it again
[15:37] <Riddell> Filesystem      Size  Used Avail Use% Mounted on
[15:37] <Riddell> /dev/sdb1       2.7T   17G  2.6T   1% /media/muckle
[15:37] <Riddell> nice storage :)
[15:37] <shadeslayer> @    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
[15:38] <shadeslayer> Riddell: whoa :O
[15:38] <shadeslayer> Riddell: did you reinstall from scratch?
[15:38] <Riddell> yes I reinstalled it for the new bits of hardware I got
[15:39] <shadeslayer> Riddell: can't login
[15:39] <shadeslayer> my password was changed?
[15:41] <Riddell> shadeslayer: well yes your account got wiped, I can set it up again if that's useful
[15:41] <shadeslayer> yes plz
[15:41] <shadeslayer> you also want to install fail2ban on the machine
[15:42] <Riddell> shadeslayer: username?
[15:42] <Riddell> what's fail2ban?
[15:42] <shadeslayer> shadeslayer
[15:42] <shadeslayer> !fail2ban
[15:43] <shadeslayer> !info fail2ban
[15:44] <Riddell> shadeslayer<EMAIL_ADDRESS>[16:08] <shadeslayer> Riddell: did you connect the disk via usb?
[16:18] <Riddell> shadeslayer: yeah, so it'll be slow
[16:19] <shadeslayer> :(
[17:12] <shadeslayer> Riddell: any ideas why SSL validation is failing?
[17:13] <shadeslayer> bzr: ERROR: [Errno 1] _ssl.c:509: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
[22:29] <Riddell> ScottK: https://launchpad.net/ubuntu/+source/pykde4/4:4.11.1+git20130916-0ubuntu3  :)
[22:57] <Riddell> https://twitter.com/sil/status/381552058895462401  :)
[23:23] <shadeslayer> go go Riddell


[07:28] <saifheld> Hello everyone, I just signed up to the volunteer list, I'd like to join your translators "section" if possible
[07:29] <saifheld> I added my email, and which language I can translate to in the wiki page.
[07:29] <saifheld> And surely I subscribed to the LP page.
[07:33] <UndiFineD> hello saifheld
[07:34] <UndiFineD> which language(s) do you know ? :) your help is appreciated
[07:36] <UndiFineD> currently translations are done in bazaar
[07:36] <UndiFineD> as launchpad .po file translations would make the source grow tremendously
[07:37] <UndiFineD> the textfiles are reduced html content
[07:37] <saifheld> I'm from Jordan, so my mother tongue is Arabic.
[07:38] <UndiFineD> :D
[07:38] <saifheld> Sadly I never worked with Bazaar before, but hey I've to learn at some point if I want to participate in the community.
[07:38] <UndiFineD> I dont think we have such a language yet
[07:38] <saifheld> "Noticed" and I'm furious about it! =P
[07:39] <UndiFineD> have a look at our website, it is not that difficult
[07:39] <saifheld> Yeah I browsed it briefly, and I'm excited to help out.
[07:40] <saifheld> I'm no hardcore-developer , nor programmer by anymeans, I'm a self-learner and I've a lot to learn
[07:40] <saifheld> But this is what I can do for now "not ashamed =P"
[07:40] <UndiFineD> great, good to have you here then
[07:41] <saifheld> Glad to be here.
[07:41] <saifheld> I'll start finding out what Bazaar is, install it..
[07:41] <saifheld> If I run into troubles I'll contact you..(all)
[07:42] <UndiFineD> there is bazaar explorer, or you can work with it from the commandline as explained on our website
[07:42] <saifheld> If I wanna send an introduction to other members, is it ok to do it via the email-list?
[07:42] <UndiFineD> yes that is fine
[07:42] <saifheld> That's cool.
[07:42] <saifheld> Thanks =)
[07:43]  * UndiFineD blinks aprilg ? I have not seen you in a while
[07:43] <aprilg> hey UndiFineD
[07:43] <aprilg> am just lurking..
[07:43] <UndiFineD> :)
[07:43] <aprilg> really busy with the transition to a new job
[07:43] <UndiFineD> oh great
[07:44] <UndiFineD> so you have a happy home then
[07:44] <aprilg> UndiFineD: it's ok, i guess :)
[07:44] <UndiFineD> kids alright ? excited about christmas
[21:43] <MichealH> UndiFineD: Bot aint working? :P
[21:43] <UndiFineD> maintenance :)
[21:43] <MichealH> Ahh


[05:10] <cem____> anybody can help
[06:55] <micahg> \o/ gimp 2.8.0 released (waiting for it to trickle into Debian)
[09:17] <ochosi> micahg: yay!
[17:11] <mips1911> Anyone know what the cause of the bug is that causes your title bars and window borders to disappear?
[17:25] <ochosi> mips1911: i guess otherwise it'd be fixed
[17:25] <ochosi> mips1911: does it happen in 12.04 as well?
[17:28] <mips1911> ochosi, no idea, I only had it happen to me once or twice in 11.10, currently only have xubuntu base install + openbox installed, waiting for 4.10 ppa
[17:29] <ochosi> mips1911: so you mean the bug happens with openbox?
[17:29] <mips1911> ochosi, weren't the devs gonna add some code to autostart it once it crashed, recall somehting like that
[17:29] <ochosi> that should happen anyway (session manager takes care of that)
[17:30] <mips1911> oh ok
[21:13] <pleia2> added to reviews http://linuxblog.darkduck.com/2012/05/xubuntu-1204-dont-fix-what-is-not.html
[21:14] <Unit193> Broken.
[21:14] <pleia2> ?
[21:16] <Unit193> dont-fix-what-is-not.html, I had to finish it. :/
[21:17] <pleia2> oh :)
[22:01] <mips1911> Merci beaucoup monsieur pouit ;)
[22:01] <mips1911> I see the PPA is live
[22:15] <mips1911> mr_pouit, getting unmet dependencies for the ppa, http://paste.ubuntu.com/965704/
[22:25] <mips1911> mr_pouit, never mind I see things are still in waiting to build status, will check back in the morning
[22:26] <ochosi> was just about to say that...
[22:30] <mips1911> I got all excited and never checked the status and just went ahead with the install. Hopefully when I wake up in the morning I will have a present waiting for me.
[22:31] <ochosi> not unlikely, mostly depends on what else the buildservers have on their plate
[22:34] <mips1911> g'night, 00:30 here sso i'm off to bed


[21:56] <tsimonq2> Hey, wxl, quick question. When we migrate from LXDE to LXQt, will my custom panel settings stay the same, or will they be ported? If that answer is no, then how easy would it be to migrate the settings during the port...
[21:57] <tsimonq2> wxl: Or rather the migration
[21:58] <tsimonq2> And if wxl can't answer, can someone else answer? Kamilion ianorlin phillw
[21:58] <tsimonq2> Unit193:
[21:58] <Kamilion> ?
[21:58] <tsimonq2> Read
[21:58] <ianorlin> tsimonq2: no the settings for the panel are different
[21:58] <tsimonq2> So I would have to tweak them all over again?
[21:58] <Kamilion> Dunno, havn't gotten a chance to play with lxqt at all myself
[21:59] <ianorlin> yeah but the applets are different
[21:59]  * Kamilion returns to task
[21:59] <tsimonq2> Are there applets with the same functions?
[22:00] <tsimonq2> Take a look at my panel ianorlin
[22:00] <tsimonq2> http://imgur.com/4fXmXe7
[22:02] <tsimonq2> Can I do that in LXQt ianorlin?
[22:02] <tsimonq2> ianorlin: Or no?\
[22:05] <tsimonq2> ianorlin: I have to leave. Send me an email with an answer. My email is on my wiki page(wiki.ubuntu.com/tsimonq2).
[22:20] <Unit193> Hrm.
[22:20] <Unit193> Well, anyway.  Different application, different settings.
[22:30]  * Kamilion sighs
[22:31] <Kamilion> http://imgur.com/gallery/DZqeyOO  <--- now I'm stuck browsing imgur


[06:50] <bzoltan> sil2100: I have one last failing test here -> https://requests.ci-train.ubuntu.com/static/britney/ticket-1511/vivid/excuses.html should pass after retry
[06:50] <sil2100> o/
[06:51] <sil2100> bzoltan: let me try re-running, internet here is terrible
[06:51] <bzoltan> sil2100: thank you
[06:51] <sil2100> bzoltan: ok, recycled (it seems), yw!
[07:37] <bzoltan> sil2100: Do you remember why Timo has suggested to do triple landing for the UITK. He must had some good reason.
[07:46] <sil2100> bzoltan: I guess it's because it's the default thing to do, per requirement
[07:47] <sil2100> bzoltan: do you have any other propositions? :)
[07:53] <bzoltan> sil2100:  i do not... I am happy with the tripple landing, because it gives me clear visibility on how the UITK builds on Yakketi. But QA are unhappy about the fact that i had to disable the unit tests on Yakketi. Qt is newer on Yakketi and because of this we have failing tests.
[07:55] <sil2100> Ah, eh... yeah, the biggest issue with triple landing everywhere is that you have to somehow support 3 distros at once, make sure they're all good
[07:55] <sil2100> bzoltan: did you guys disable only for yakkety? i.e. are those running for xenial/vivid still?
[07:57] <bzoltan> sil2100:  of course we have disabled it only for Yakketi. We do run all the tests on Vivid and on Xenial.
[07:58] <sil2100> bzoltan: ok, good - how many tests had to be disabled? All of them, or just parts?
[07:58] <sil2100> I could check that myself but the internet is so slow here ;)
[08:02] <bzoltan> sil2100:  I simple disabled all the unit tests on Yakketi.  Yakketi is not released, not an official target and there is no supported device out there with Yakketi. At this stage we are happy that UITK builds on Yakketi and I wish to keep my eyes on the Yakketi buildsű
[08:04] <sil2100> Yeah, I suppose it's feasible for now
[08:05] <sil2100> We just don't want to have the devel series without unit tests forever ;)
[08:14] <bzoltan> sil2100:  Yes, of course. But I hope the QA team will understand that it is not like "yeah, we have added some code what makes tests fail, so we disabled the tests". It is simple because the Qt is newer on Yakketi and we have to invest couple of weeks to investigate the reason and polish together the Qt and UITK.  It is exacty what we have done since 5.0 Qt many times. But the first step is to build the packages...
[08:23] <sil2100> bzoltan: yeah, I wouldn't directly block on that right now at least, as long as there's commitment to get it working soon (with a bug and assigmnent etc.)
[08:27] <bzoltan> sil2100: definetly there is commitment. This is the bug - https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1591908 And i will look after it once we are good with the OTA12
[08:27] <sil2100> bzoltan: excellent, good enough for me :)
[08:27] <sil2100> Thanks!
[09:55] <pstolowski> rvr, hey, there are a couple of autpkg failures in silo 65 for unity8 on xenial which look like flaky tests to me, they seem completely unrelated to my recent changes; unfortunately it seems Saviq's team is still recovering from the sprint, not sure if they are going to be online today to check & confirm
[09:57] <rvr> pstolowski: Ok
[11:29] <Trevinho> robru: it would be a nice addition, but will the auto-updating build page (jenkins style) page be back in the future?
[11:30] <robru> Trevinho: you mean live-streaming the log output?
[11:30] <Trevinho> robru: yeah
[11:30] <robru> Trevinho: yeah that is planned. I actually had one implementation already but I had to cut it at the last second because it was buggy
[11:30] <Trevinho> ah i see
[11:31] <robru> Trevinho: probably I'll implement git support before going back and making the logs stream.
[11:31] <Trevinho> yeah, that's definitely higher priority
[11:32] <Trevinho> robru: oh, just noticed a thing...
[11:33] <robru> Trevinho: yeah?
[11:33] <Trevinho> robru: I changed the commit message for a MP, and once I rebuilt the pkg, it did't get updated
[11:33] <Trevinho> robru: no, wait...
[11:33] <robru> Trevinho: is this another case of you running two builds really quickly back to back?
[11:34] <Trevinho> robru: no, I just was checking wrong build :-), sorry
[11:34] <robru> Trevinho: no worries.
[11:34] <robru> Trevinho: you can always check at https://code.launchpad.net/~ci-train-bot to see what the latest build committed.
[11:37] <Trevinho> robru: you might want to see this audit log, though https://requests.ci-train.ubuntu.com/#/ticket/1482#audit_log not sure you want to show the error in that way
[11:37] <robru> Trevinho: yeah there's a bug for that already, thanks
[11:45] <dbarth> rvr: i approved the branches in silo 39
[11:45] <rvr> dbarth: Great, thanks
[12:34] <cjwatson> robru: I might have accidentally got excited at the weekend and implemented 75% or so of bug/MP linking for git
[12:35] <robru> cjwatson: haha awesome
[12:35] <robru> cjwatson: in the MPs?
[12:35] <sil2100> \o/
[12:36] <cjwatson> yeah, the idea is that you can link bugs directly to MPs; in the bzr case that'll actually add a link to the source branch for compatibility etc., in the git case it'll store a link between the bug and the MP directly
[12:36] <robru> cjwatson: you'll have to send me some API overview for when I finally get a chance to start git support.
[12:36] <cjwatson> and git MPs will automatically scan the commits between target and source for LP: references in the commit messages like in changelogs
[12:36] <robru> oh snap
[12:36] <robru> nice
[12:37] <cjwatson> robru: once I land this I think you can just change merge.source_branch.linked_bugs to merge.linked_bugs and it'll work for both
[12:38] <robru> cjwatson: oh, amazing. thanks
[12:38] <cjwatson> robru: haven't got it up for review yet, I need to do the boring bits like tests and debugging the UI into existence :)
[12:38] <robru> cjwatson: boooooring!
[12:38]  * cjwatson is a naughty boy and doesn't tend to do TDD for complicated things
[12:38] <robru> cjwatson: I have a very sophisticated test suite called "end users"
[12:39] <cjwatson> oh, we have a very sophisticated test suite, I just don't always do the fancy thing where you exhibit a failing test first :)
[12:40] <robru> cjwatson: heh, yeah, me too.
[12:40] <sil2100> Testing is overrated, cowboying things direct-to-production is more like it
[12:40] <sil2100> Faith in our code is all we need!
[12:40] <cjwatson> anyway, 1400 lines of diff at the moment, so will probably turn into about three or four branches
[12:43] <robru> cjwatson: oh no way, whenever my branch goes over 1,000 lines I just get barry to review it. hehehe
[12:49] <cjwatson> robru: LP prefers <=800 lines per review where we can manage it
[12:50] <robru> cjwatson: well that seems sensible as long as you can divide your work into bite-size chunks
[14:10] <kenvandine> rvr, the autopkgtest failure for silo 22 is unity8, not related to this landing.  Can you get silo 22 in ready for QA please?
[14:25] <rvr> kenvandine: pstolowski: tsdgeos: I see there are common unity8 failures in silo 22 and in silo 65.
[14:26] <rvr> mzanetti: ping
[14:27] <kenvandine> rvr, yeah... not uncommon, lately it seems we see that on all of our settings landings
[14:28] <pstolowski> rvr, kenvandine according to tsdgeos these tests are not very stable.. and i suppose mzanetti is recovering from the sprint
[14:28] <tsdgeos> he's on holiday
[14:29] <pstolowski> ah ok
[14:29] <tsdgeos> will be bck ~wed ~thu afair
[14:29] <rvr> pstolowski: I was pinging him for silo 29, not related :D
[14:29] <rvr> But thanks
[14:29] <pstolowski> k :)
[14:36] <rvr> tsdgeos: Can you take a look to those recurring failing tests?
[14:37] <rvr> marcustomlinson: ping
[14:37] <marcustomlinson> rvr: pong
[14:38] <rvr> marcustomlinson: Hi. I'm testing silo 29
[14:38] <rvr> marcustomlinson: "add libertine-scope to the list of exceptions that can directly activate things"
[14:38] <marcustomlinson> rvr: I'm really sorry, I had to abandon that one
[14:38] <marcustomlinson> rvr: pstolowski landed that change in silo 1
[14:38] <rvr> marcustomlinson: Oh
[14:39] <marcustomlinson> rvr: I'm really sorry. That was a communication fail
[14:39] <rvr> Meh, we should update the trello bot to catch up with abandon silos
[14:39] <tsdgeos> rvr: doesn't look very recurring to me, at least the ones that pstolowski showed me before were not consistent on errors of amd64 vs intel
[14:39] <marcustomlinson> rvr: oh, it's not landed there yet. https://requests.ci-train.ubuntu.com/#/ticket/1515
[14:39] <rvr> tsdgeos: I see common failures in silo 65 and 22
[14:39] <tsdgeos> rvr: can you point me at the logs?
[14:40] <marcustomlinson> rvr: I guess pstolowski is still testing it
[14:40] <rvr> I had a reboot and lost my notes, let me check
[14:40] <rvr> marcustomlinson: Ok, no problem
[14:40] <kenvandine><EMAIL_ADDRESS>[14:40] <pstolowski> marcustomlinson, rvr silo 1 needs to wait for silo 65
[14:40] <pstolowski> so i'm not testing it yet
[14:40] <marcustomlinson> ok
[14:40] <kenvandine> tsdgeos, ^^
[14:40] <rvr> Yeah, search for XFAIL
[14:41] <kenvandine> tsdgeos, yakkety and vivid passed
[14:41] <tsdgeos> rvr: xfail is not a fail
[14:41] <rvr><EMAIL_ADDRESS>[14:41] <tsdgeos> rvr: you know that right?
[14:42] <rvr> tsdgeos: Argh :-/
[14:42] <tsdgeos> fail!
[14:42] <tsdgeos> is a failure
[14:42] <tsdgeos> xfail is expected fail
[14:42] <tsdgeos> and is good
[14:43] <kenvandine> FAIL!  : qmltestrunner::PhoneStage::test_selectAppFromSpread(App 3) property state
[14:43] <kenvandine>    Actual   (): 2
[14:43] <kenvandine>    Expected (): 1
[14:43] <kenvandine>    Loc: [/tmp/autopkgtest.eomPQZ/build.LIN/unity8-8.12+16.04.20160527/tests/qmltests/Stages/tst_PhoneStage.qml(113)]
[14:43] <rvr> tsdgeos: Yeah, sorry. Too much time doing manual tests :-(
[14:44] <kenvandine> that test has nothing to do with system-settings, for example
[14:44] <rvr> FAIL!  : qmltestrunner::PhoneStage::test_selectAppFromSpread(App 3)
[14:45] <kenvandine> so it shouldn't hold up a settings silo
[14:45] <rvr> That one is in 22 and 65
[14:46] <tsdgeos> kenvandine: i already said that
[14:46] <tsdgeos> i can say it again
[14:46] <tsdgeos> if it helps :D
[14:46] <kenvandine> sorry, i missed that part :)
[14:46] <tsdgeos> i told that to pstolowski this morning in a different hcannel
[14:46] <tsdgeos> not here
[14:49] <tsdgeos> i'm going to try to reproduce/stabilize it anyway
[14:49] <rvr> tsdgeos: Great, thanks
[14:52] <rvr> sil2100: Do you know which spell to use in order for a silo with a failed Automated Signoff to be set as QA Signoff Ready? jibel is not available today.
[14:57] <sil2100> rvr: hmmm, one moment, let me think
[14:58] <sil2100> (and check logs)
[15:04] <sil2100> rvr: which silo was that?
[15:05] <rvr> sil2100: 22 and 65
[15:07] <sil2100> Damn, can't find that log
[15:08] <sil2100> rvr: ok, I think I did it
[15:08] <sil2100> Not sure if that's the way to do it, for 22
[15:08] <kenvandine> sil2100, thanks!
[15:08] <sil2100> rvr: 22 is now 'Ready'
[15:08] <rvr> sil2100: Yeah, seems so
[15:08] <sil2100> rvr: what I did is: "I cleared the Lander signoff and then put it to Approved again, and then changed QA signoff"
[15:09] <sil2100> rvr: ^ ignore that 'Approved', a miss-click from my side
[15:09] <sil2100> rvr: try that for 65
[15:10] <rvr> sil2100: Hmm... the automated signoff is queued, so it may fail later
[15:10] <sil2100> Yeah, but the QA sign-off is set, it won't reset it
[15:10] <rvr> sil2100: But I think at least the card will appear
[15:10] <sil2100> (from what I know)
[15:10] <rvr> sil2100: Ah
[15:10] <sil2100> Anyway, I go EOD now since it's dinner time here
[15:11] <sil2100> (sprinting)
[15:48] <pstolowski> rvr, silo 65 still blocked on your dashboard?
[15:49] <rvr> pstolowski: Didn't receive a new card
[15:49] <rvr> Let me see now
[16:08] <pstolowski> rvr, thanks!
[17:46] <robru> rvr: sil: no you need to put "https://foo" into the manual downloads field then bileto releases control of the qa field and you can set it to whatever
[17:47] <dobey> robru: ^^ "PPA/bzr version mismatch" huh?
[17:48] <robru> dobey: did you just build? Usually that sorts itself out after 15 minutes
[17:48] <dobey> robru: yeah
[17:49] <robru> dobey: it means the ppa contents doesn't match what's it pushed to lp bzr, which could be indicative of a ppa upload failure, but it's racy
[17:50] <dobey> robru: right, that's why i'm confused. the PPA upload worked and is building, and the version number looks right to me :)
[17:51] <robru> dobey: so it'll fix itself on the next run, which is every 15 mins.
[17:51] <dobey> ok
[18:57] <bzoltan> robru:  that unity8 there here https://requests.ci-train.ubuntu.com/static/britney/ticket-1511/xenial/excuses.html seems to be running for aaaaages. Do you know somebody who could check if it is alive?
[18:59] <robru> bzoltan: if you click "test in progress" and grep for the silo name you can see
[19:00] <dobey> http://autopkgtest.ubuntu.com/running.shtml#pkg-unity8
[19:04] <robru> bzoltan: so it isn't running. Ping pitti