[00:17] <slangasek> infinity: verification done on rsyslog for bug #1187808
[00:17] <ubot2`> Launchpad bug 1187808 in rsyslog (Ubuntu Raring) "PreserveFQDN fix introduces regression that might cause rsyslog not to start" [Critical,Fix committed] https://launchpad.net/bugs/1187808
[02:52] <phillw> hi SRU people, the link from https://wiki.ubuntu.com/StableReleaseUpdates#Procedure section 4 points to a link at https://answers.launchpad.net/launchpad/+question/140509 which reports it as being wrong. Can someone look into this before the classroom session due on https://wiki.ubuntu.com/Testing/Activities/Classroom/Saucy#Reporting_Bugs Many thanks
[03:32] <phillw> Hi JackYu how has the new release worked?
[03:47] <ScottK> phillw: Did you notice it's a wiki?  I fixed it, but nothing you couldn't have done too.
[03:49] <phillw> ScottK: 1) it is referring to MOTU 2) I could not state 100% that my alteration would be correct without asking for someone to check it. In that case, I would prefer an SRU member to correct it as you do need to request confirmation that work has been done correctly :D
[03:50] <phillw> *as you do NOT need* :P
[03:53] <ScottK> Just because I'm in the team, doesn't mean I don't make mistakes.
[03:53] <ScottK> The correction that was needed was all about how LP works and nothing to do with SRU process.
[03:54] <phillw> ScottK: that was this early morning session, for a new bug triager :) Hey, we even admitted to most destructive mistakes we have learned by :)
[03:55] <ScottK> It's a wiki.  It's trivial to revert mistakes.
[03:57] <phillw> knome: I disagree, but am not going into an argument over where the 'best' and 'most accurate' information should be. https://wiki.ubuntu.com/Testing/Activities/Classroom/Instructors
[04:09] <infinity> ScottK: Were you releasing raring's rsyslog too?
[04:09] <infinity> ScottK: (I was just about to do raring and precise, and then noticed you'd just done precise)
[04:20] <phillw> knome: Sorry I mis - pinged you, it was meant for ScottK ^^
[04:24] <ScottK> infinity: I looked for raring and didn't see it.
[04:24] <ScottK> Go ahead.
[04:25] <infinity> ScottK: Alrighty.
[04:25] <infinity> Just didn't want double-copies messing up -changes. :)
[04:25] <ScottK> OK.
[04:26] <infinity> I also decided to let maas loose, so you can stop trying not to care about that one.
[04:26] <ScottK> OK, although it wasn't taking a lot of effort on my part.
[11:20] <cjwatson> Rebuilding today's desktop images - I think they failed due to component mismatches
[11:39] <ogra> cdimage@nusakan:~$ for-project ubuntu-touch cron.daily-preinstalled --live && /home/ogra/utouch-android/do-zip-android
[11:39] <ogra> lockfile: Forcing lock on "/srv/cdimage.ubuntu.com/etc/.lock-build-image-set-ubuntu-touch-saucy-daily-preinstalled"
[11:39] <ogra> do i have to be worried ?
[11:41] <cjwatson> ogra: maybe?
[11:42] <cjwatson> I don't see any other builds running though
[11:43] <ogra> there shouldnt
[11:43] <cjwatson> That'd be the main worry, so I guess you can ignore it unless it happens again and then we'll investigate
[11:44] <ogra> k
[13:13] <ogra> hmm, i wonder if that build is stuck ... still havent gotten my prompt back
[13:19] <shadeslayer> infinity: my email is still broken :(
[13:19] <shadeslayer> infinity: should I just open a ticket on rt.ubuntu.com ?
[16:01] <bdmurray> cjwatson: at the client sprint you'd suggested testing Phased-Update-Percentage (for the dice rolling changes) with quantal.  Is there a particular reason you suggested Q?
[16:03] <cjwatson> I did?
[16:03] <cjwatson> Um, I don't remember :)
[16:04] <bdmurray> we were talking with slangasek about how update-manager rolls the dice on a binary package basis and how this might create a problem with dependencies and how update-manager should be changed to roll the dice for source packages
[16:04] <cjwatson> Right, I remember the discussion, but I can't think why I would have suggested quantal
[16:05] <cjwatson> Unless it was something to do with a release that I thought might be less in use so safer to fiddle with, or something
[16:05] <bdmurray> ah okay, so testing with raring seems fine then?
[16:05] <cjwatson> Yeah, I think so
[16:05] <bdmurray> its easier to backport the calculation change to R than Q
[16:06] <cjwatson> Thanks for working on that
[16:07] <bdmurray> No problem
[16:19] <infinity> shadeslayer: I've poked again, but if that poke goes nowhere, a ticket might be good.
[16:20] <infinity> shadeslayer: In fact, yes, please file a ticket so it doesn't get lost.
[16:20] <infinity> shadeslayer: Give me the RT number, and I'll make sure it's someone's priority.
[16:22] <infinity> bdmurray: I never take "we should test $feature_foo on $release" at face value, especially right after a release. :P
[16:22] <infinity> bdmurray: Heck, I'm still writing raring^wsaucy in changelogs.
[16:30] <bdmurray> infinity: could you run this for me?  it's me upload
[16:30] <bdmurray> s/me/my/
[16:30] <bdmurray> remove-package -m "The verification failed in Precise and actually it doesn't need fixing." -d ubuntu -s precise-proposed -e 0.16.2  apport-symptoms
[16:31] <ScottK> bdmurray: If infinity doesn't answer up in a minute or two, I'll run it.
[16:31] <infinity> I'm on it.
[16:32]  * infinity double-checks that it's bdmurray's upload and he's not socially engineering him.
[16:33] <bdmurray> heh
[16:33] <infinity> bdmurray: What about the one in raring that is the same patch?
[16:33] <bdmurray> infinity: I just released that one I thought
[16:34] <infinity> 'Published 51 seconds ago'
[16:34] <infinity> Indeed.  I was too quick. :)
[16:34] <bdmurray> the issue is that ubuntu-release-upgrader-core doesn't exist in P so the symptom does nothing
[16:35] <infinity> bdmurray: Oh, indeed, it's update-manager-core in precise.
[16:36] <infinity> bdmurray: Removed.
[17:10] <bdmurray> infinity: you removed gnome-keyring from precise-propsed, it looks like the same problem will exist with the package upload in the unapproved queue for quantal
[17:10] <bdmurray> see bug 1094319 for details
[17:10] <ubot2`> Launchpad bug 1094319 in gnome-keyring (Ubuntu Quantal) "p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory" [Undecided,In progress] https://launchpad.net/bugs/1094319
[17:20] <infinity> bdmurray: If it has the same incorrect Replaces/Breaks, it will, yep.
[17:21] <infinity> bdmurray: And it does.  Rejecting.
[18:20] <bdmurray> infinity: thanks!
[18:20] <infinity> bdmurray: NP.  Thanks for spotting it before someone else accepted. :)