[08:08] <mardy> Mirv: hi! Do you know where I can find an older version of the uitk (I'd like to try 1.3.1742+15.04.20151209-0ubuntu1 to verify if a bug I'm seeing is a regression in the uitk)?
[08:08] <mardy> Mirv: ops, nevermind, got it :-)
[08:25] <Mirv> mardy: ok :)
[09:20] <davmor2> sil2100: are we having the landing meeting this morning I assume it will be you and me
[09:21] <sil2100> davmor2: there might be Mirv as well ;)
[09:21] <sil2100> davmor2: let's do a quick one, you know, to say merry christmas and such!
[09:22] <davmor2> sil2100, Mirv: there had better be cats is all I can say ;)
[09:23] <sil2100> I think our cat is busy around my girl's grandmother now ;)
[09:25] <Mirv> davmor2: sure, two of them
[09:26] <davmor2> Mirv \o/
[09:55] <sil2100> dbarth: ping! Could you top-approve https://code.launchpad.net/~mardy/gnome-control-center-signon/invalid-providers-1287640/+merge/279278 ?
[10:20] <davmor2> bfiller: Elleo: was browser app in silo 17 rebuilt, it doesn't look it or it failed judging by the crosses, if you can hit that today we can get that landed then
[10:21] <Elleo> davmor2: will trigger a rebuild now
[10:22] <Elleo> oSoMoN: are the failures for webbrowser-app on ppc arm64 s390x, etc. a normal thing? I notice the train doesn't flag them
[10:23] <Elleo> davmor2: oh, looks like silo 45 still hasn't landed yet
[10:23] <Elleo> davmor2: it's blocked on an oxide/gcc issue that's preventing it building for xenial
[10:23] <oSoMoN> Elleo, yes, failures for those arches are expected, because oxide doesn’t build on them
[10:24] <davmor2> Elleo: should of sil2100 triggered an new image with it in on friday
[10:24] <Elleo> oSoMoN: ah, okay; thanks
[10:24] <davmor2> sil2100: ^
[10:24] <davmor2> ah okay
[10:24] <Elleo> davmor2: on the train it's listed as manual published for vivid, while waiting for oxide xenial fix
[10:24] <Elleo> (silo 45 that is)
[10:24] <oSoMoN> Elleo, davmor2: I’m looking into the issue, but it’s like a pandora box, it uncovered a bunch of issues which all need to be fixed for it to work
[10:24] <davmor2> Elleo: right okay
[10:25] <davmor2> oSoMoN: :'(
[11:16] <dbarth> sil2100: ack
[11:17] <dbarth> sil2100: hey, what about the oxide compiler issue? is there a possibility to revert to the previously known-to-work compiler?
[11:17] <dbarth> sil2100: i know oxide was dictating the gcc build dep a few months ago, for similar reasons
[11:29] <davmor2> Mirv: awesome now I can insult you here to.....insult......insult.........insult ;)
[11:31] <Mirv> davmor2: :D
[11:32] <Mirv> davmor2: I can feed your insult machine. We're still not publishing the latest UITK landing to xenial.
[11:32] <Mirv> (due to unability to build webbrowser which doesn't build because oxide-qt doesn't build on armhf because of new GCC 5.3)
[11:32] <davmor2> Mirv: Shuggin fashin shuggin fashin insult insult random insult pfff fine
[11:33] <davmor2> Mirv: right but what does that have to do with uitk
[11:34] <davmor2> Mirv: also that will mean no more dual landing fullstop
[11:34] <Mirv> davmor2: nothing, but your insult machine can surely blame SDK team for it anyway! :)
[11:34] <dbarth> Mirv: on that cascade of issues, see what i was writing to sil2100; can that help ?
[11:34] <dbarth> or otherwise let us know if we need to do an emergency call to Chris
[11:35] <sil2100> Yeah, still thinking what to do here
[11:35] <Mirv> davmor2: it has that to do that webbrowser needs to land together with UITK (like it did to vivid) but compiler issue now hold the xenialn one
[11:35] <sil2100> LP: #1527741
[11:35] <sil2100> I think reverting to an earlier gcc is not an option
[11:36] <Mirv> dbarth: it's probable it's purely GCC ARM problem still, so Chris can't help
[11:38] <sil2100> I guess it could be fixed on oxide side as well, probably gcc became more strict or something
[11:40] <sil2100> Looks really strange tho, would have to check the source but that would take ages
[11:40] <sil2100> ;)
[11:41] <dbarth> yeah
[11:42] <dbarth> and also it feels like a code change that should be backed by upstream
[11:42] <dbarth> when they want blink or v8 to be gcc 5 compatible
[11:52] <sil2100> dbarth: looks like currently we're in a deadlock then... chrisccoulson is on holidays, not really possible to back-out gcc, hm
[12:12] <sil2100> bfiller: hey! Regarding silo 46 - I can't publishi this silo due to ubuntu-ui-extras
[12:13] <sil2100> bfiller: normally manual re-builds like this can be ignored, but there's actually a change missing that's required
[12:13] <sil2100> bfiller: ubuntu-ui-extras needs to have the libexiv2-13 hard-coded dependency dropped
[12:14] <sil2100> bfiller: (change introduced by 0.2+15.04.20150311-0ubuntu3)
[12:19] <Saviq> sil2100, can you publish https://requests.ci-train.ubuntu.com/#/ticket/725 ?
[12:20] <davmor2> john-mcaleely: I see no issues with the tarball
[12:21] <john-mcaleely> davmor2, excellent
[12:21] <john-mcaleely> sil2100, any reason I should not push the tarballs now?
[12:21] <sil2100> john-mcaleely: no, all good
[12:21] <sil2100> Saviq: hmm, looks published to me
[12:22] <sil2100> Saviq: I published this on Friday
[12:23] <john-mcaleely> sil2100, pushed. thank you
[12:24] <sil2100> john-mcaleely: thanks :)
[12:26] <Saviq> sil2100, oh, sorry, it's not obvious unless you read the status line, sorry :)
[12:27] <sil2100> nw ;)
[12:27] <Saviq> ah but we have regressions in qtmir-gles apparently
[12:28] <Saviq> hmm
[12:29] <Saviq> ok /me confused
[12:34] <Saviq> sil2100, can you please upload qtmir-gles with http://paste.ubuntu.com/14127400/ to xenial-proposed (and stable-phone-overlay for good measure...)?
[12:36] <Mirv> Saviq: which silo, could it be direct upload to the silo + re-publish? anyway, I can help
[12:36] <Saviq> sil2100, or shall I better prepare a qtmir silo with those changes
[12:36] <Saviq> Mirv, https://requests.ci-train.ubuntu.com/#/ticket/725
[12:36] <Mirv> Saviq: ah so no silo, just stuck?
[12:36] <Saviq> Mirv, I can do silo if that's better
[12:36] <Saviq> no-qa needed
[12:36] <Mirv> Saviq: broken in overlay too so emulator broken?
[12:37] <Saviq> Mirv, it's not really broken
[12:37] <Mirv> Saviq: ok
[12:37] <Mirv> Saviq: silo is always nicer, one gets the diff from the build job etc that's easier to double-check
[12:37] <Saviq> Mirv, ok will do
[12:38] <Saviq> Mirv, problem is new autopkgtest approach seems to have proposed pinned under archive, which IIUC means unless you request a version from proposed explicitly it won't take it
[12:38] <Saviq> sil2100, we need to pay more attention to -gles diffs, thus ↑
[12:38] <Mirv> Saviq: hmm, but, that ticket isn't merge&cleaned? if you get the silo, I can upload manual uploads there and then we can double-check the diff.
[12:39] <Saviq> Mirv, or we could force merge&clean as qtmir-gles is the last thing stuck and make it unstuck with the new silo asap
[12:40] <Mirv> Saviq: yeah autopkgtests have something like that, or that they are not dist-upgraded. bug #1524817 is about that when upgrading new Qt version, old libqt5test5 is installed and does not get upgraded to the newer version
[12:40] <Saviq> Mirv, problem is in qtmir-gles autopkgtests it tries to build against mir 0.17
[12:40] <Saviq> it's a somewhat dumb autopkgtest...
[12:40] <Mirv> Saviq: it sounds pretty similar to the Qt problem - it first setups build dependencies from release pocket, then enables proposed pocket and installs only strict requirements or something like that
[12:40] <Saviq> even though the package was built in silo against 0.18
[12:41] <Saviq> but really it did find an issue with our deps, so it's a valid problem
[12:41] <Saviq> s/problem/test/
[12:41] <Mirv> Saviq: I'm merge & cleaning now
[12:41] <Saviq> Mirv, ok, I'll have silo asap
[12:46] <Mirv> Saviq: trunks are now up-to-date
[12:50] <Saviq> kdub, need a hand please to unblock Mir from xenial-proposed https://code.launchpad.net/~mir-team/qtmir/gles-sync/+merge/280396
[12:50] <Saviq> https://code.launchpad.net/~saviq/qtmir/no-change/+merge/281090
[12:50] <Saviq> https://requests.ci-train.ubuntu.com/#/ticket/809
[12:51] <kdub> Saviq, what's needed?
[12:51] <Saviq> kdub, review of those two MPs please
[12:51] <Saviq> kdub, we might've told you wrong about the -gles sync MP requirements, debian/control needs to be updated manually
[12:51] <sil2100> Saviq: well, qtmir-gles did not generate any packaging diffs so those were not reviewed
[12:52] <Saviq> sil2100, yeah, which should blink a red light from now on (if there are debian/ changes in non-gles)
[12:52] <kdub> Saviq, done, looks good
[12:53] <Saviq> sil2100, I try to remember myself when landing anything with -gles, but if it gets through still
[12:53] <Saviq> kdub, thanks
[12:53] <kdub> Saviq, Saviq, https://docs.google.com/document/d/1VOP_I1dn_9oxwwf209S0ANGOYeOuROmARoOeyth8QaE/edit#heading=h.i57dat7acs4s
[12:53] <kdub> step 13d is the qtmir / gles instructions for the mir team
[12:54] <kdub> Saviq, I'm guessing they should be changed to always bump the version number?
[12:55] <Saviq> kdub, any changes in non-gles debian/ need to be "ported" to -gles debian/, if applicable
[12:57] <Saviq> kdub, I've proposed a change to the step
[13:04] <kdub> thanks Saviq
[13:05] <sil2100> Saviq: true ;)
[13:05] <kdub> Saviq, and if i understand, mir is stuck, pending 809 landing?
[13:06] <Saviq> kdub, stuck for xenial, yes, should be under an hour
[13:09] <kdub> Saviq, ack, thanks for the help. The changes to the doc made sense, thanks for the edit
[13:11] <Saviq> Mirv, any idea what's with https://requests.ci-train.ubuntu.com/#/ticket/796 ? is it stuck somehow due to the oxide-qt mess?
[13:11] <Saviq> it seems to be published to vivid overlay, but not even in proposed for xenial
[13:35] <Mirv> Saviq: it's purposefully not released to xenial since it would break things since webbrowser-app is not possible to build. so it's better for it not to be there at all than to break xenial images. currently GCC regression causes oxide-qt to fail to build on armhf
[13:35] <Saviq> Mirv, builds done, train doesn't seem to have caught up yet https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-021 https://requests.ci-train.ubuntu.com/#/ticket/809
[13:35] <Saviq> Mirv, not a gcc regression any more, according to the bug, but yeah, I understand
[13:36] <Mirv> Saviq: well it sounds like a change in GCC anyway, any failure, since it built fine just two weeks ago
[13:37] <Saviq> Mirv, might still be valid issues though, just not shown before
[13:37] <Mirv> Saviq: and some bounds checking sounds like a gcc change
[13:38] <Mirv> Saviq: diffs look good https://ci-train.ubuntu.com/job/ubuntu-landing-021-1-build/7/
[13:39] <Mirv> jibel: heads up url above ^ no-change rebuild of qtmir going into overlay silo soon
[13:39] <Mirv> small dependency change for qtmir-gles
[13:50] <bfiller> sil2100: just seeing your message. little confused about what I should do on silo 46. It looks to have built correctly on both distros in the silo
[13:51] <sil2100> bfiller: yes, but you need to include the downstream change
[13:51] <sil2100> bfiller: since slangasek didn't release that to the archive for nothing - just remove the dependency and remove
[13:51] <sil2100> http://launchpadlibrarian.net/213415209/ubuntu-ui-extras_0.2%2B15.04.20150311-0ubuntu2_0.2%2B15.04.20150311-0ubuntu3.diff.gz
[13:51] <bfiller> sil2100: oh so he pushed something to the archive and not to trunk you mean?
[13:51] <sil2100> s/remove/rebuild
[13:51] <sil2100> Yeah... bad practice
[13:52] <bfiller> sil2100: got it, ok
[13:52] <sil2100> But that was during the wily finals, so he's excused partially ;)
[13:52] <sil2100> bfiller: thanks!
[14:07] <Mirv> Saviq: so, should you set 021 to publish without QA and let's publish it?
[14:07] <Saviq> Mirv, dnoe
[14:07] <Saviq> done, even
[14:12] <Mirv> Saviq: published, let's hope autopkgtests pass this time
[14:21] <bfiller> sil2100: what's the best way to get the changelog in sync with what's in archive? getting this error trying to build https://ci-train.ubuntu.com/job/ubuntu-landing-046-1-build/4/console
[14:22] <bfiller> sil2100: nm, just will copy from version in wily
[15:11] <davmor2> sil2100: silo 58 were you able to deal with that in the end?
[15:12] <davmor2> Mirv: so qt-networking silo 5, I assume that it is just double checking that nothing breaks on the phone with networking right then it can be landed?
[15:13] <davmor2> Mirv: assume that kenvandine will soon tell you if it doesn't work, iirc the thing that was throwing us was that the phone has no ethernet :)
[15:13] <Mirv> davmor2: that should be it yes.
[15:14] <Mirv> davmor2: ken has confirmed the fix at bug #1523975
[15:14] <davmor2> Mirv: cool
[15:25] <kdub> Saviq, just to check, once https://requests.ci-train.ubuntu.com/#/ticket/809 goes through, mir will become unstuck? I admittedly don't know the process very well
[15:26] <Saviq> kdub, yeah, everything will happen automagically, should be any minute now
[15:26] <kdub> cool, thanks for the help
[15:27] <Saviq> kdub, you can monitor the progress on http://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#qtmir and http://autopkgtest.ubuntu.com/running.shtml
[15:27] <kdub> ah neat, didn't know about those sites
[15:28] <sil2100> davmor2: yeah, it's done
[15:29] <Saviq> kdub, the first one is linked in the "Status" line in https://requests.ci-train.ubuntu.com/#/ticket/809
[15:29] <davmor2> sil2100: great I'll delete the ticket from the qa list then
[15:54] <bfiller> sil2100: silo 46 has been rebuilt and problems fixed with ui-extras package, should be able to publish now
[15:55] <sil2100> bfiller: \o/ thanks, on it now
[17:33] <jhodapp> Mirv, can you publish silo 34 for me please since it needs a core dev to land?
[17:53] <kdub> is this silo stuck? https://requests.ci-train.ubuntu.com/#/ticket/809
[18:11] <jhodapp> cyphermox, around?
[18:11] <cyphermox> yep
[18:12] <jhodapp> cyphermox, my silo 34 got QA approval, can you please land it since it needs a core dev to do so?
[18:22] <cyphermox> jhodapp: NAK, the changelog there means nothing at all, it doesn't even describe the changes in the patch: https://ci-train.ubuntu.com/job/ubuntu-landing-034-1-build/lastSuccessfulBuild/artifact/qtmultimedia-opensource-src-gles_vivid_packaging_changes.diff
[18:23] <jhodapp> cyphermox, that's for the -gles package which was not changed, I'm not quite sure what Mirv does for that
[18:23] <jhodapp> cyphermox, the change is really in the non -gles package
[18:24] <jhodapp> cyphermox, and actually, that description is accurate
[18:24] <cyphermox> well then why does it need a patch?
[18:24] <cyphermox> and why not just write what the patch does?
[18:25] <jhodapp> cyphermox, it does, it's a sync
[18:25] <cyphermox> that's not a sync, that's copying the same changes again to another package
[18:25] <jhodapp> cyphermox, that's what the -gles package is
[18:25] <cyphermox> and that brings up the question of why do you need two source packages when it's the same code?
[18:25] <jhodapp> I don't fully understand what it's used for
[18:26] <jhodapp> cyphermox, not sure, you'd have to ask Mirv as he's the real maintainer of this for Ubuntu
[18:27] <cyphermox> I'd very much like to see better changelogs even if it's just copying the same thing from one package to another. that's the point of changelogs, making sure people who don't have all the context have an idea of what's going on
[18:28] <jhodapp> cyphermox, sure ideally I agree...we can get Mirv to update this although I'm pretty sure this is how things have always been done
[18:29] <cyphermox> jhodapp: it's not because it's how it always has been done that it's correct
[18:29] <jhodapp> cyphermox, I never said that :)
[18:29] <cyphermox> we've been able to do multiple builds of different kinds with a single source package :)
[18:29] <jhodapp> cyphermox, I really can't answer your questions, we need to get an explanation from Mirv
[18:29] <cyphermox> indeed.
[18:30] <cyphermox> well, I don't feel it's necessary that I punish you because of this, but I'll bring up the issues to Timo
[18:30] <jhodapp> cyphermox, alright, we need a better way of reviewing source only package changes...this kind of discussion should happen before I'm asking a core dev to land it
[18:31] <cyphermox> well, yes and no
[18:31] <cyphermox> people should already know to write meaningful changelogs
[18:31] <cyphermox> in fact, it flows from writing meaningful commit messages :)
[18:32] <jhodapp> cyphermox, agreed, but this should be caught in a code review process like a normal MR, but this isn't an MR
[18:32] <cyphermox> what wasn't a MR?
[18:32] <jhodapp> cyphermox, this change, it's a source package only change
[18:32] <cyphermox> people who do direct uploads should even better know to write changelogs
[18:33] <Elleo> trainguards: heya, I've just retargetted silo 17 from dual landing to vivid only, I seem to remember there was some manual clean up needed in the past when doing this, am I remembering right?
[18:33] <jhodapp> cyphermox, but anyway, thanks for publishing
[18:33] <jhodapp> and reviewing it
[18:34] <cyphermox> sure
[18:35] <cyphermox> Elleo: I'm not sure what trainguards are around for this. did you try to rebuild? I would expect this to be the only thing needed.
[18:35] <Elleo> cyphermox: I haven't tried yet, I just remembered having to ping someone for something last time I did this :P
[18:36] <Elleo> cyphermox: I'll give it a go and see what happens
[18:36] <cyphermox> ok
[18:51] <jhodapp> robru, around?
[19:36] <kdub> trainguards,  https://requests.ci-train.ubuntu.com/#/ticket/809 seems stuck somehow waiting for ubuntu-system-settings-online-accounts
[19:36] <kdub> not quite sure why... is there something that can be done to move the ticket along?
[19:58] <cjwatson> kdub: it appears to be waiting for autopkgtests in general to catch up
[19:59] <cjwatson> kdub: but at least some of the relevant tests are running right now
[19:59] <kdub> cjwatson, so its just going slow, not stuck then?
[20:00] <kdub> I'm not quite sure the details of this process, kinda looks stuck to me
[20:00] <cjwatson> kdub: slow
[20:00] <cjwatson> kdub: http://autopkgtest.ubuntu.com/running.shtml shows the relevant tests urnning
[20:00] <cjwatson> *running
[20:00] <kdub> cjwatson, thanks for the help
[20:20] <robru> cyphermox: agreed, stupid -gles not being built from the same source package has been a thorn in my side for a long time. IIRC according to slangasek it's because they have mutually conflicting build deps that they have to be separate source packages
[20:21] <robru> jhodapp: hey what's up?
[20:21] <cyphermox> robru: that's be the one good reason to have those separate
[20:22] <robru> Elleo: you can't just retarget, you need to branch your changelog for vivid as the train won't allow generating a vivid version number on a xenial trunk
[20:23] <robru> Also you'll need me to delete the xenial packages manually
[20:23] <robru> Generally you should fix whatever issue is not working in xenial rather than five up on it and try to release to vivid only
[20:24] <robru> cyphermox: yeah I tried making it all coinstallable one time and it was a giant fustercluck
[20:26] <jhodapp> robru, hey, can you please dput qtmultimedia 5.4.1 from ppa:jhodapp/ubuntu/ppa to silo 58
[20:27] <pmcgowan> robru, that silo is blocked by a gcc5 issue in xenial such that a lib oxide needs wont compile
[20:27] <bzoltan_> robru:  may I ask for a silo to fix that system settings issue - https://requests.ci-train.ubuntu.com/#/ticket/814 ?
[20:28] <robru> pmcgowan: OK well you'll need a new branch with a vivid changelog then
[20:28] <pmcgowan> not sure if Elleo or oSoMoN  are still around
[20:28] <pmcgowan> bfiller, ^
[20:29] <pmcgowan> thats for silo 17
[20:30] <bfiller> pmcgowan: looking
[20:30] <robru> jhodapp: done
[20:31] <oSoMoN> pmcgowan, robru: I’m around
[20:32] <robru> bzoltan_: hm I would but I'm having trouble with sso...
[20:32] <oSoMoN> robru, we’ve not given up, but any xenial webbrowser-app build is blocked on bug #1528297, and no one will take a look at it until tomorrow at the earliest
[20:33] <robru> oSoMoN: ok but if you switch your silo from dual to vivid you're essentially giving up on xenial ;-)
[20:33] <bzoltan_> robru: right... whenever you can :) i will be back
[20:33] <oSoMoN> robru, temporarily
[20:33] <oSoMoN> robru, although from what you said, if we need to branch we might as well revert to dual landing and do like we did for silo 45, i.e. force merge with a broken package in xenial
[20:34] <robru> oSoMoN: if you're planning on switching it back to dual before landing I recommend just leaving it as dual and just letting the xenial builds fail until they get fixed later. because you can't just take a xenial trunk and build it for vivid, you have to branch the trunk, not worth the effort
[20:34] <oSoMoN> robru, okay
[20:34] <robru> right
[20:34] <oSoMoN> Elleo, still around?
[20:35] <oSoMoN> I’ll update the landing request to revert to dual landing
[20:36] <robru> cyphermox: if you're able to log in to train jenkins can you assign https://requests.ci-train.ubuntu.com/#/ticket/814 ? I can't seem to log in
[20:36] <cyphermox> done
[20:37] <robru> cyphermox: thanks
[21:10] <Elleo> oSoMoN: back now
[21:12] <oSoMoN> Elleo, I reverted silo 17 to dual-landing and triggered a rebuild, it’s almost done now, I’ll be testing it just to double check, and we can ask davmor2 to give his ok tomorrow morning
[21:13] <Elleo> oSoMoN: okay, cool
[21:14] <oSoMoN> Elleo, feel free to do some quick validation on your side as well, I wouldn’t want to break anything the day I leave for holidays
[21:20] <Elleo> oSoMoN: is the "diff missing" message anything to be concerned about?
[21:20] <Elleo> oSoMoN: will install now and run through some quick sanity checks
[21:20] <oSoMoN> Elleo, I don’t know, but it doesn’t look like the train considers it a blocking error
[21:21] <Elleo> oSoMoN: okay
[21:27] <alecu> Hi trainguards, I get "ERROR Assignment failed: Low on silos: Ask a trainguard to assign.", so I guess I need to ask y'all.
[21:27] <alecu> https://requests.ci-train.ubuntu.com/#/ticket/816
[21:29] <robru> cyphermox: can you assign another? I still can't log in
[21:30] <cyphermox> robru: can you try again? there should be no reason why you can't log in... otherwise it would be good to ask on launchpad-ops.
[21:30] <robru> cyphermox: the status in #is-outage mentions sso being unresponsive for some people
[21:32] <alecu> outage again? :-(
[21:42] <robru> alecu: train is fine I just can't log in because sso
[21:44] <robru> cyphermox: I'm chatting with #is people, if you could go ahead and assign https://requests.ci-train.ubuntu.com/#/ticket/816 that'd be super, th
[21:44] <robru> thx
[21:45] <cyphermox> ok
[21:45] <cyphermox> SUCCESS
[21:46] <alecu> yay, santa got here earlier!
[21:46] <alecu> thanks guys :-)
[21:47] <cyphermox> what? where is it?
[21:47] <cyphermox> what I want for christmas is to be able to breathe normally again
[21:48] <alecu> cyphermox: really? what happened?
[21:48] <cyphermox> just a cold
[21:48] <cyphermox> but then I get annoyed at myself for generating so much mucus, coughing, runny eyes and all.
[21:50] <alecu> sounds annoying... hope you get well!
[21:50] <cyphermox> in due time! :)
[21:57] <robru> cyphermox: thanks
[22:00] <cjwatson> kdub: ah, yeah, maybe it is in fact stuck - not something I have the ability to fix I'm afraid
[22:20] <robru> awwwwwwww yissssssss ^ new queuebot won't ping spam nearly so much now ;-)