=== zul_ is now known as zul
[13:31] <joshuahoover> pitti: ping
[13:31] <pitti> hi joshuahoover
[13:32] <joshuahoover> pitti: hi! can you take a look at bug #726597 an sru for desktopcouch in lucid
[13:32] <ubot4`> Launchpad bug 726597 in desktopcouch (Ubuntu Lucid) (and 3 other projects) "desktopcouch can start multiple times leading to several running couchdbs (affects: 2) (heat: 255)" [High,Fix committed] https://launchpad.net/bugs/726597
[13:34] <pitti> joshuahoover: is that fixed in maverick/natty?
[13:34] <joshuahoover> pitti: yes, afaik
[13:34] <pitti> joshuahoover: it's still shown as open; can you please check and close?
[13:35] <joshuahoover> pitti: sure...where are you seeing it as open for maverick/natty? (must be missing it)
[13:36] <pitti> joshuahoover: the main ubuntu package task is "in progress", as well as the upstream tasks
[13:36] <joshuahoover> pitti: ah, ok...yeah, let me make sure it's fixed in maverick/natty and i'll update
[13:37] <pitti> joshuahoover: aside from this, just upload it to the queue; much easier to review/accept from there
[13:37] <pitti> (or, rather, it _must_ be reviewed from the queue anyway)
[13:38] <joshuahoover> pitti: got ya...ok
[14:57] <joshuahoover> pitti: ok, i verified bug #726597 is fixed in maverick/natty and marked the bug appropriately...we have an upload waiting for approval - https://launchpad.net/ubuntu/lucid/+queue?queue_state=1
[14:57] <ubot4`> Launchpad bug 726597 in desktopcouch (Ubuntu Lucid) (and 3 other projects) "desktopcouch can start multiple times leading to several running couchdbs (affects: 2) (heat: 14)" [High,Fix committed] https://launchpad.net/bugs/726597
=== ogra is now known as Guest56191
=== Guest56191 is now known as ogra_
[15:04] <pitti> joshuahoover: cool, thanks
[15:06] <joshuahoover> pitti: thank you :)
=== jjohansen is now known as jj-afk
[16:03] <Riddell> someone is doing ~ubuntu-archive package removals?
=== TheHarald is now known as apachelogger
=== jj-afk is now known as jjohansen
[20:49] <GrueMaster> skaet: Did I miss something?  I was told we weren't assigning bugs to teams?  Re:  Bug 727468.
[20:49] <ubot4`> Launchpad bug 727468 in webkit (Ubuntu Natty) (and 5 other projects) "ubiquity-slideshow tears down oem-config on armel (affects: 1) (heat: 10)" [High,Confirmed] https://launchpad.net/bugs/727468
[21:06] <skaet> GrueMaster,  30-40 unassigned high/critical bugs makes it hard to figure out if 1) bug is on a team's radar, just no-one available to work on it.  or 2) its in limbo,  and we need to find an owner.   Assigning to teams at least lets us flesh out the limbo ones.
[21:07] <GrueMaster> I have no problem with this.  Just checking to see if I had missed a proc change.  :P
[21:08] <GrueMaster> I am trying to monitor the armel tagged bugs on a weekly basis.  A lot of cruft in the older releases that I am working to either bring current or close completely.
[21:08] <skaet> There seem to be many different processes in place...  so I'm trying to standardize them a bit.
[21:08] <GrueMaster> Sounds good.
[21:09] <ogra_> we usually subscribe ubuntu-armel during the triage but thats indeed less easy to see than an assignment
[21:09] <GrueMaster> If you ever have any questions on armel related bugs, don't hesitate to ask.
[21:09] <skaet> Do you want me to add armel tags as well,  when I spot cross team ones?
[21:09] <ogra_> armel tags shouldnt be bound to teams
[21:10] <ogra_> onyl to the HW
[21:10] <GrueMaster> No.  bugs should only have armel tags when they are specific to armel.
[21:10] <GrueMaster> When I go through and triage current bugs, I sometimes remove that tag if I can reproduce it on x86 & amd64.
[21:16] <GrueMaster> The other thing I should point out is that not all armel bugs are worked on by the canonical-arm team.  Most toolchain bugs are worked on by linaro for example.
[21:16] <ogra_> many others too
[21:29] <skaet> GrueMaster, ogra_ https://bugs.launchpad.net/ubuntu/+source/gcc-4.5/+bug/721531 is this likely to get fixed for Natty?
[21:29] <ubot4`> Launchpad bug 721531 in gcc-4.5 (Ubuntu Natty) (and 2 other projects) "[armel] gcc computes wrong address for main() at build time (affects: 1) (heat: 172)" [High,Triaged]
[21:29] <ogra_> skaet, up to linaro
[21:29] <skaet> ogra_,  thanks.
[21:29] <slangasek> that's incorrect
[21:30] <ogra_> they own toolchain and compiler
[21:30] <slangasek> rather, if it's up to linaro then the answer is "no" - this is an upstream gcc 4.5 issue that Linaro is not able to commit to fixing
[21:31] <slangasek> (as noted in https://bugs.launchpad.net/ubuntu/+source/gcc-4.5/+bug/721531/comments/11)
[21:31] <ubot4`> Launchpad bug 721531 in gcc-4.5 (Ubuntu Natty) (and 2 other projects) "[armel] gcc computes wrong address for main() at build time (affects: 1) (heat: 141)" [High,Triaged]
[21:31] <ogra_> right, but essential linaro is our channel to talk to upstream or about any toolchain/compiler issues
[21:31] <ogra_> essentialy
[21:32] <GrueMaster> So it is correct that linaro is the first point of contact for this issue, but it doesn't look like it will be fixed in natty.
[21:32] <ogra_> thats what the last comment says
[21:32] <ogra_> (in the bug)
[21:32] <GrueMaster> yep
[21:34] <slangasek> skaet: so I don't think assigning it to the Linaro TCWG is correct as they've already indicated they don't have the resources to work on that this cycle
[21:34] <slangasek> s/correct/useful/, I should say
[21:35] <skaet> slangasek, okie,  I'll move it to oneiric.   It was useful in that it forced this discussion to happen ;)
[21:35]  * skaet trying to identify the bugs in limbo, and get them moved...
[21:38] <slangasek> ogra_: I'm not sure why you would limit yourselves to using Linaro as a conduit for talking to upstream; if the bug is reproducible in FSF gcc 4.5, and Linaro TCWG aren't working on the issue in question, they're just a middleman
[21:38] <slangasek> skaet: right, ok :)
[21:43] <skaet> GrueMaster, do you know if anyone's actively looking at https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/726811
[21:43] <ubot4`> Launchpad bug 726811 in emacs23 (Ubuntu) "[natty] emacs23/armel FTBFS (affects: 1) (heat: 247)" [Critical,Confirmed]
[21:44] <ogra_> skaet, FTBFS is currently mostly handledby janimo
[21:45]  * ogra_ shakes his head about "Critical"
[21:45]  * GrueMaster changed it to high.
[21:46] <GrueMaster> Critical is when it ftbfs on all platforms and is needed for image building.
[21:46] <ogra_> hmm, looks like compiler or toolchain looking at the build log
[21:46] <ogra_> or buildd :P
[21:47] <GrueMaster> Didn't we get a new gcc recently?  Maybe retrigger the build?
[21:47] <ogra_> yup
[21:49] <ogra_> given back, lets see
[21:52] <skaet> ogra_, GrueMaster - have marked it as canonical arm developers,  since it your team is working it right now.   Feel free to assign directly to janimo if appropriate if it looks to still be an issue after the builds.
[21:52] <ogra_> i'm not working on it, i clicked a button on a website :P
[21:53] <GrueMaster> but that involves work, right?
[21:53] <ogra_> and i'm fairly sure it will just build
[21:53] <skaet> https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/726827  looks similar
[21:53] <ubot4`> Launchpad bug 726827 in mutter (Ubuntu Natty) (and 1 other project) "[natty] mutter/armel FTBFS (affects: 1) (heat: 10)" [High,Confirmed]
[21:53] <GrueMaster> I mean, you had to move the mouse or something.
[21:53] <ogra_> GrueMaster, its 11pm here, i dont work at that time of day
[21:53] <GrueMaster> :P
[21:54] <ogra_> so it must have been a sparetime confision of my mouse :)
[21:54] <ogra_> *confusion
[21:55] <skaet> :)