[00:03] <yofel> another very patient reporter - https://bugs.launchpad.net/bugs/625676
[00:03] <ubot2> Launchpad bug 625676 in apt (Ubuntu) "Infinite loop in dpkg: Hang at 'Unpacking' (affects: 1) (heat: 8)" [Undecided,New]
[00:03] <yofel> *sigh*
[00:06] <jpds> yofel: Nice.
[00:06]  * penguin42 has some sympathy when you have a bug that's broken stuff for you and you're sitting there banging your head against the keyboard
[00:18] <hggdh> yofel: are you going to answer?
[00:18]  * hggdh is curious
[00:19] <yofel> not for now, I'm too tired to write anything that doesn't sound frustrated, maybe I'll remeber how to get debug info out of dpkg too until tomorrow
[00:19]  * hggdh has not much sympathy for someone that forcefully does something (bad), and then complains it is broken
[00:41] <kermiac> vish:  Yay! Thanks mate :)
[01:00] <hggdh> ah well. I answered the OP
[02:02]  * devildante is bored... do you have any bugs you would want to get fixed?
[02:07] <kermiac> devildante: there's literally thousands of bugs out there mate... ever played 'eeny meeny'? :P
[02:07] <devildante> kermiac: programmer = lazy = can't find bugs on his own :p
[02:08] <persia> devildante, Any restrictions on that?  I'd be happy to see 531155 get some sorting
[02:08] <kermiac> haha
[02:08] <devildante> bug 531155
[02:08] <ubot2> Launchpad bug 531155 in gedit (Ubuntu) (and 1 other project) "gedit schemas is not registered during live session (affects: 2) (dups: 1) (heat: 23)" [Low,Invalid] https://launchpad.net/bugs/531155
[02:08] <devildante> hmm, working on an invalid bug must be cool :p
[02:09] <devildante> oh, it's gconf!
[02:09] <persia> "invalid" comes from some history of uncertainty about where the bug belongs (casper/gedit/gconf/etc.)
[02:11] <persia> bug #102664 is another suggestion, if that one seems messy.
[02:11] <ubot2> Launchpad bug 102664 in liferea (Ubuntu) "liferea does not preserve open tabs across sessions (heat: 2)" [Low,Confirmed] https://launchpad.net/bugs/102664
[02:12] <devildante> hmm, it seems the bug hasn't been updated since 2010-03-31, apart from a comment by pedro_ to ask if the issue is still present
[02:12] <devildante> bookmarking the first bug until someone responds, I guess :p
[02:12] <persia> Easy enough to verify that it's still present, really.
[02:13] <devildante> persia: don't have access to Live-CD, so I can't verify :(
[02:13] <persia> Hrm?  What sort of access don't you have?
[02:14] <devildante> persia: I don't have a CD to burn the live-cd iso (I'm talking about bug 531155)
[02:14] <ubot2> Launchpad bug 531155 in gedit (Ubuntu) (and 1 other project) "gedit schemas is not registered during live session (affects: 2) (dups: 1) (heat: 39)" [Low,Invalid] https://launchpad.net/bugs/531155
[02:14] <micahg> devildante: just use virtualbox
[02:14] <persia> And/or usb-creator
[02:15] <devildante> micahg, persia: okay... I'll run testdrive
[02:15]  * persia has mostly tested that bug with kvm in the past, but got stuck
[02:15] <devildante> looking in the second bug now
[02:15] <persia> devildante, Good luck, and thanks for asking :)
[02:15] <devildante> persia: you're welcome!
[02:18]  * devildante will log-out
[02:19] <drew212> vish: I sent my Mentee's the email, I'm  just waiting on their reply =)
[02:23] <devildante> persia: can gnome applications save state on exit/logout?
[02:34] <persia> Some of them do, so I presume so.  I believe they need to do so when sent a signal to close, so it's more about application start/finish than login/logout
[03:03] <stlsaint> drew212: ping
[03:03] <drew212> hey buddy whats up?
[03:04] <stlsaint> drew212: nm, just read your email
[03:05] <drew212> Great! Let me know if you have any questions or if you want to start on something particular. I'm doing HW at the, so i wont be able to get too in depth but i can answer any questions holding you back from getting started triaging =)
[03:05] <drew212> S/HW at the/HW at the moment
[03:10] <drew212> stlsaint: is there any package you are particularly interested in?
[03:11] <stlsaint> drew212: um, im really interested in servers
[03:11] <stlsaint> and desktop
[03:11] <stlsaint> and nvidia grapchis
[03:11] <stlsaint> :D
[03:11] <drew212> stlsaint: thats quite a list =)
[03:11] <drew212> stlsaint: anything holding you back from getting your feet wet?
[03:12] <stlsaint> drew212: just wanted to get started with a mentor in best approach
[03:12] <drew212> stlsaint: well go ahead and pick one that you think's easy and i'll try to introduce you to the workflow
[03:13] <trinikrono> drew212: so you are mentor now , nice!
[03:14] <stlsaint> drew212: hrm, i guess lets go with servers sice its my favorite
[03:14] <drew212> trinikrono: lol, yeah =D, vish kept bugging me so i said yes =P
[03:14] <stlsaint> drew212: thats cause i was bugging vish ;)
[03:14] <drew212> stlsaint: definetly, pick something you're passionate about
[03:15] <stlsaint> drew212: servers is at my top pick
[03:16] <drew212> do you know how to find bugs related to ubuntu server edition?
[03:16] <stlsaint> drew212: no :(
[03:17] <stlsaint> drew212: oh wait you mean via lp?
[03:18] <drew212> yea
[03:18] <stlsaint> oh yea gotcha
[03:23] <drew212> is there a particular package related to the server distribution you want to work on? it helps if you have a particular package in mind
[03:24] <stlsaint> drew212: hrm, i would have to look again, i didnt too very much digging into it tbh
[03:24] <drew212> stlsaint: thats fine =)
[03:27] <drew212> stlsaint: just let me know when you've found a bug you want to work on.
[03:35] <stlsaint> drew212: um how about openssh?
[03:36] <drew212> stlsaint: sure =), thats what i was looking at earlier. Do you have a bug picked out?
[03:36] <stlsaint> https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/216847
[03:36] <ubot2> Launchpad bug 216847 in openssh (Ubuntu) "sshd will not start at boot if ListenAddress is set, because network interface is not yet up (affects: 2) (heat: 31)" [Low,Confirmed]
[03:36] <stlsaint> drew212: just grabed from list :D
[03:38] <drew212> first part of triaging for me is checking if I can reproduce the bug, I don't own a server, so you're going to have to do that for me =).
[03:39] <drew212> first part for triaging confirmed bugs*
[03:40] <stlsaint> drew212: oh ok
[03:40] <stlsaint> drew212: LOL, so i could potentialy lost ssh ability on my server :P
[03:41] <stlsaint> s/lost/lose
[03:41] <drew212> i would suggest running server on a VM =)
[03:41] <drew212> dont use it on a production machine
[03:41] <persia> drew212, You could just set up openssh-server on your desktop, and `ssh localhost`
[03:41] <stlsaint> drew212: i run openvz on server, ill throw one together for bug :D
[03:41] <drew212> =)
[03:42] <drew212> persia: I'm actually not very familiar with server operations =P.
[03:43] <stlsaint> persia: noth something i would enjoy doing running openssh-client/server on lappy
[03:44] <persia> stlsaint, Why not?  Resource usage is extremely low.
[03:45] <persia> I run it on most of my laptops, because sometimes I want to get to them from my desktop at home, and use the larger screen.
[03:46] <stlsaint> persia: aye, makes sense for that
[03:47] <persia> And if you manage to break openssh-server on your laptop, it's the least potential important place :)
[03:49] <stlsaint> drew212: bug reproduced succesfully
[03:52] <drew212> ok, so the confirmed status is correct =)
[03:52] <stlsaint> drew212: yep
[03:52] <drew212> does the bug report need to have anything added to make it easier to reproduce?
[03:52] <stlsaint> drew212: nope
[03:54] <persia> Based on comment #3, it may be worth investigating whether upstart yet has the ability to support this relationship.
[03:54] <stlsaint> persia: yea i saw that
[03:54] <persia> Until that's present (or some other way around it is identified), the bug can't progress.
[03:55] <drew212> stlsaint: yeah: collin is the maintainer for openSSH =)
[03:56] <lifeless> *colin*
[03:56] <lifeless> one el
[03:57] <drew212> yes, colin =)
[03:57] <drew212> stlsaint: so that bug is 'triaged' as far as it can be for now
[03:58] <stlsaint> oooh ok
[03:58] <stlsaint> drew212: welli must go for now but tomorrow i will look for a better one and bring it to you
[03:59] <persia> It would be "triaged" a couple years ago.  With the passage of time, I think it deserves some research into the current state of upstart before changing the status.
[03:59] <drew212> stlsaint: alright =), feel free to work on them yourself to a degree you're comfortable with, be sure to read the documentation i sent in the email =)
[04:01] <stlsaint> drew212: will do
[11:29] <^arky^> Is this bug properly triaged bug 623221
[11:29] <ubot2> Launchpad bug 623221 in espeak (Ubuntu) (and 1 other project) "hungarian language phoneme is full broken and unusable (affects: 1) (heat: 10)" [Undecided,Triaged] https://launchpad.net/bugs/623221
[11:49] <^arky^> Is this bug properly triaged bug 623221
[11:49] <ubot2> Launchpad bug 623221 in espeak (Ubuntu) (and 1 other project) "hungarian language phoneme is broken and unusable (affects: 1) (heat: 10)" [Undecided,Triaged] https://launchpad.net/bugs/623221
[12:15] <vish> bah! i have around 3 bugs waiting for retracers :(
[12:18] <penguin42> you need a stick to prod them with
[12:26]  * vish stares at vish_ ..  leave!!!!
[12:27] <vish> now, thats better! ;p
[12:28] <devildante> hi all :)
[12:28]  * devildante wonders what's all this talk about retracers
[12:29] <yofel> devildante: the apport crash retracing service
[12:30] <yofel> and the fact that it happily let's you wait for eternity to give you a proper backtrace
[12:30] <devildante> haha
[12:30] <devildante> thanks yofel :)
[13:08] <^arky^> Is this bug properly triaged bug 623221
[13:08] <ubot2> Launchpad bug 623221 in espeak (Ubuntu) (and 1 other project) "hungarian language phoneme is broken and unusable (affects: 1) (heat: 10)" [Undecided,Triaged] https://launchpad.net/bugs/623221
[13:14] <kaushal> hi
[13:32] <kaushal> can someone please suggest me about https://bugs.launchpad.net/ubuntu/+source/xen-meta/+bug/540110.
[13:32] <ubot2> Launchpad bug 540110 in xen-meta (Ubuntu) "ubuntu-xen-server has broken dependencies (dup-of: 538917)" [Undecided,New]
[13:32] <ubot2> Launchpad bug 538917 in xen-tools (Ubuntu) "xen-tools is not available in lucid (affects: 25) (dups: 2) (heat: 110)" [Undecided,New]
[13:39] <devildante> kaushal: confirm bug 548917
[13:39] <ubot2> Launchpad bug 548917 in mountall (Ubuntu) "lucid won't boot from nfs because of mountall.conf (dup-of: 537133)" [Undecided,New] https://launchpad.net/bugs/548917
[13:39] <ubot2> Launchpad bug 537133 in portmap (Ubuntu Lucid) (and 3 other projects) "mountall issues with NFS root filesystem (affects: 15) (dups: 2) (heat: 103)" [Medium,Fix released] https://launchpad.net/bugs/537133
[13:39] <devildante> fail
[13:39] <devildante> kaushal: confirm bug 538917
[13:39] <ubot2> Launchpad bug 538917 in xen-tools (Ubuntu) "xen-tools is not available in lucid (affects: 25) (dups: 2) (heat: 110)" [Undecided,New] https://launchpad.net/bugs/538917
[13:40] <yofel> ^arky^: if espeak upstream is Debian then yes.
[13:42] <devildante> yofel, seems upstream is espeak.sourceforge.net
[13:43] <yofel> seems so, but I can't find the bug tracker for some reason
[13:49] <kaushal> devildante: is there a fix for it
[13:49] <kaushal> i didnot understand that
[13:49] <kaushal> I mean as per bug < devildante> kaushal: confirm bug 538917
[13:49] <ubot2> Launchpad bug 538917 in xen-tools (Ubuntu) "xen-tools is not available in lucid (affects: 25) (dups: 2) (heat: 111)" [Undecided,New] https://launchpad.net/bugs/538917
[13:50] <devildante> kaushal: I meant, set status as confirmed
[13:51] <kaushal> devildante: ok
[13:51] <kaushal> so no fix uptill now ?
[13:51] <kaushal> I mean no workaround
[13:51] <kaushal> Just wanted to understand
[13:53] <yofel> not really, as we ubuntu doesn't have the package in neither lucid nor maverick currently
[13:54] <thekorn> mvo: hi, can you help me with bug 626740: if a .desktop file shipped with app-install-data has a typo, in this case the typo must be fixed in the original package, right?
[13:54] <ubot2> Launchpad bug 626740 in app-install-data-ubuntu (Ubuntu) "String 3871 typo (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/626740
[13:56] <mvo> thekorn: yeah, we can patch it short term in app-install-data, but most of that data is auto-generated
[13:56] <devildante> hi, mvo :) Do you have any idea of what's causing bug 623819? (since you fixed it, I thought you might know why it is/was happening)
[13:56] <ubot2> Launchpad bug 623819 in policykit-1-gnome (Ubuntu) "[Maverick] policykit is not responding (affects: 129) (dups: 6) (heat: 616)" [Medium,Fix committed] https://launchpad.net/bugs/623819
[13:57] <mvo> devildante: yes, was not implementing the full session managment protocol
[13:58] <devildante> mvo: is it fixed upstream as well?
[13:59] <mvo> devildante: it was a distro patch, but that one should probably be send upstream
[13:59] <mvo> devildante: the rational is that we want the agent to be availalbe and one of the best ways to ensure this is by registerng so that its auto-restarted on crashes/errors
[14:00] <thekorn> mvo: ok, thanks. A user reported a few typos in some desktop files during the last few days, I will change the target now
[14:01] <mvo> thekorn: thanks! what is the bugnumber (just out of curiosity)
[14:02] <thekorn> mvo bug 625877, bug 626735, bug 626740
[14:02] <ubot2> Launchpad bug 625877 in app-install-data-ubuntu (Ubuntu) "String 3592 typo (affects: 1) (heat: 6)" [Undecided,Confirmed] https://launchpad.net/bugs/625877
[14:02] <ubot2> Launchpad bug 626735 in app-install-data-ubuntu (Ubuntu) "String 3862 typo (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/626735
[14:02] <ubot2> Launchpad bug 626740 in app-install-data-ubuntu (Ubuntu) "String 3871 typo (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/626740
[14:02] <thekorn> (I was alarmed by the short title ;))
[14:03] <devildante> mvo: can you merge https://code.edge.launchpad.net/~ilidrissi.amine/update-manager/update-manager.fix-624894/+merge/33855, please? ;)
[14:12] <mvo> devildante: that is merged in trunk already :) its pending in the review-queue
[14:12] <devildante> thanks mvo :)
[14:12] <mvo> :)
[14:12] <mvo> yw
[14:13] <mvo> devildante: I merged the branch as "meged"
[14:13] <mvo> devildante: I mean, I *marked* it as merged (can't type today ;)
[14:13] <devildante> mvo: ah yeah
[14:13] <devildante> mvo: what about https://code.edge.launchpad.net/~ilidrissi.amine/software-center/fix-conflicting-packages/+merge/33818 ?
[14:20] <devildante> hi kamusin :)
[14:21] <kamusin> hey devildante , how are things there?
[14:22] <devildante> kamusin: all is fine :)
[14:23] <kamusin> heh super, like a monday morning :)
[14:24] <devildante> kamusin: not exactly morning, it's 1:24 PM here :p
[14:24] <kamusin> doh'
[14:59] <ta_bu_shi_da_yu> hi, I can't seem to connect to au.archive.ubuntu.com when I run a build-dep of openoffice.org
[14:59] <ta_bu_shi_da_yu> anyone have any ideas what's going on here?
[15:02] <kklimonda> ta_bu_shi_da_yu: try a different mirror
[15:02] <ta_bu_shi_da_yu> kklimonda, how do I go about doing this?
[15:05] <ta_bu_shi_da_yu> actually, silly me
[15:05] <ta_bu_shi_da_yu> quite easy, just forgot how
[15:05] <ta_bu_shi_da_yu> cheers
[17:45] <bdmurray> thekorn: so the fix for bug 320596 was a bit more involved but has landed ;-)
[17:45] <ubot2> Launchpad bug 320596 in malone "Series.searchTasks() always returns an empty collection (affects: 1) (dups: 2) (heat: 34)" [High,Fix committed] https://launchpad.net/bugs/320596
[18:04] <thekorn> bdmurray: great, thanks. Is this fix already available on edge or stable?
[18:05] <njin> Hello, what is a dead-stroke key ? https://bugs.launchpad.net/ubuntu/+bug/431922
[18:05] <ubot2> Launchpad bug 431922 in ubuntu "dead_stroke broken in some applications (affects: 1) (heat: 16)" [Undecided,Incomplete]
[18:05] <bdmurray> thekorn: yes on edge
[18:06] <thekorn> ok, let me verify it's working
[18:08] <thekorn> bdmurray: list(hardy.searchTasks()) still gives me an empty list on edge :(
[18:08] <thekorn> bdmurray: http://pastebin.ubuntu.com/485917/
[18:12] <bdmurray> thekorn: use version='devel'
[18:12] <bdmurray> thekorn_: use version='devel'
[18:14] <thekorn_> bdmurray: aha, ok. It's looking much better now.
[18:14] <thekorn_> thanks for fixing this bug
[18:27] <devildante> seb128: why did you unassign me bug 572381? After all, I'm working on it, and that's the meaning of assignments :p
[18:27] <ubot2> Launchpad bug 572381 in rhythmbox-ubuntuone-music-store (Ubuntu) (and 1 other project) "Ubuntu One Store not showing (affects: 3) (heat: 18)" [High,In progress] https://launchpad.net/bugs/572381
[18:27] <seb128> devildante, because I though your part was done and that u1 guys needed to review it now
[18:28] <seb128> devildante, if it's not assigned to their team it might just fall off their tracking
[18:28] <devildante> seb128: ah... okay, sorry for bothering you :)
[18:28] <seb128> no worry
[18:28] <seb128> sorry if you were not done hacking on it
[18:29] <devildante> seb128: no, I'm done :)
[19:08] <neeraj> >	for bug 511225, should I file a ff'e request separately?
[19:08] <ubot2> Launchpad bug 511225 in sugar-0.88 (Ubuntu) "running sugar causes left-click not to work properly in GNOME (affects: 2) (heat: 34)" [Critical,Confirmed] https://launchpad.net/bugs/511225
[19:10] <devildante> neeraj, I don't think so, since you're fixing a bug and not adding a feature
[19:15] <neeraj> devildante: Ok. thanks for replying. its a bug fix patch only. Actually i was wondering because the patch was in review stage for a long time . Other patches that I had added were approved much quickly
[19:16] <devildante> neeraj: next time, subscribe ubuntu-sponsors to the bug when you have a debdiff ;)
[19:16] <devildante> (I've done this for you already)
[19:21] <neeraj> devildante: ohh.. my bad.. thanks again.. one last query.. I have to fix one more bug for sugar-0.88 bug 617582
[19:21] <ubot2> Launchpad bug 617582 in sugar-0.88 (Ubuntu) "When opening the control panel some icons are cut off . (affects: 2) (heat: 338)" [High,In progress] https://launchpad.net/bugs/617582
[19:23] <neeraj> here, i was confused what should be the revision number of the package.. I mean ubuntu2 is in queue..(like in sponsor) and I am not sure that I can directly jump from ubuntu1 to ubuntu3
[19:24] <neeraj> This thing has been bothering me for a long time. I mean if there are number of bugs in a package and different people are working on it. then how do we make sure the package name along with version and revision number does not get conflict
[19:25] <devildante> neeraj: the sponsors take care of this, I think
[19:26] <devildante> neeraj: of course, if a sponsor review request got accepted, it would be nice of you to fix the conflict
[19:32] <devildante> neeraj: for now, just put ubuntu2 ;)
[19:33] <neeraj> devildante: thanks for the pointers :).. I was just wandering here and there for past 1 hr :)..
[19:33] <neeraj> thanks a lot..
[19:49] <njin> 64-bit - Not recommended for daily desktop usage   http://www.ubuntu.com/desktop/get-ubuntu/download    Why ???
[19:50] <penguin42> njin: Flash is the biggest problem; aren't many others
[19:50] <micahg> njin: I would guess since people might d/l the 64 bit version and it might not run on their machine
[19:50] <micahg> penguin42: flash works fine for me in 64 bit
[19:50] <penguin42> micahg: You running 64bit or with nsplugin ?
[19:51] <njin> I use 64 bit from two years and i've not great problem..
[19:51] <micahg> penguin42: nspluginwrapper, 64 bit flash has many security issues at this point
[19:51] <penguin42> micahg: Yeh, I run with nspluginwrapper and it's not bad these days but it still dies from time to time
[19:51] <penguin42> but hey maybe that's no worse than 32bit
[19:52] <njin> Thanks guys .
[21:00] <mmix-chagsub> hey guys if a op is complaining about problems with sound it should be filed against the kernel correct?
[21:01] <mmix-chagsub> or i can just put bug 627038 and someone will help me out hopefully
[21:01] <ubot2> Launchpad bug 627038 in ubuntu "Sound for sound card "Gembird SC-5.1-1" based on VT1723 chip, detected as ICE1724 is not starting with system every time (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/627038
[21:34] <bdmurray> jibel: do you think we could stop apport-package bugs that include "Read-only file system" in DpkgTerminalLog.txt?
[21:40] <jibel> bdmurray, hm, I don't think of a case that would hurt.
[21:41] <jibel> bdmurray, but it usually need to be crossed checked with the content of dmesg
[21:42] <jibel> bdmurray, e.g. if there is a failure because of a file system being RO then check in dmesg if the file system is mounted RO.
[21:44] <jibel> bdmurray, It would be great if we could do the same for device failures. Usually there is an apport-package error showing an I/O error and dmesg shows a medium error or device exception.
[21:52] <jibel> bdmurray, we were talking about the regression-* tags with pedro and hggdh.
[21:52] <jibel> bdmurray, do you know why the regression-potential was introduced ?
[21:54] <bdmurray> jibel: to keep track of regressions that might show up in the development release of Ubuntu
[21:55] <jibel> bdmurray, okay but why not use the regression-release and target the dev release ? Today it's hard to know which regression are 'maybe a regression' and which are confirmed regressions
[21:55]  * hggdh starts paying attention
[21:55] <jibel> bdmurray, and when the dev release is released, we need to confirm all the regression-potential and change them to regression-release.
[21:57] <bdmurray> jibel: I see your point and I'm not positive of why but I think the tag was used to denote the state of the regression and regression-release meant regression-releaseD
[21:57] <jibel> bdmurray, I triaged nearly 40 bugs tagged release-potential (linux excluded)  and only 2 where correctly tagged
[21:58] <bdmurray> jibel: and why were the tagged incorrectly? should they have been regression-release or were they not regressions at all?
[21:58] <hggdh> the point is a lot of regression -potential bugs are left after the -dev is released
[21:59] <hggdh> they were (probably) regressions in development, but then (for example) lucid became 10.04, and the bugs are still tagged regression-potential
[21:59] <bdmurray> hggdh: well we should have cleaned them up / reviewed them in April or May
[22:00] <hggdh> indeed. But it sounds better, now, to tag them regression-release + ubuntu version, and use regression-potential for something that *may* be a regression
[22:00] <bdmurray> I'm not attached to regression-potential however it seems easier to query on ubuntu.searchTasks(tag=reg-pot) than maverick.searchTasks(tag=reg-pot)
[22:01] <jibel> bdmurray,  the idea is to use regression-potential to mean 'this is maybe a regression'
[22:01] <hggdh> on any release
[22:01] <jibel> bdmurray, and when it's confirmed change to 'regression-release' and target the affected release.
[22:02] <jibel> as hggdh on any release.
[22:02] <drew212> is there any specific reason i'm getting timeout errors when searching on LP for certain packages, specifically firefox?
[22:02] <hggdh> drew212: using edge?
[22:03] <bdmurray> Having people tag regressions using regression-release then targetting to the release when they are "confirmed" on that release seems simpler to me
[22:03] <drew212> hggdh: not as far as i know, idk what edge is
[22:03] <hggdh> drew212: edge.launchpad.net, the test LP instance
[22:04] <hggdh> bdmurray: indeed. And we considered that regression-potential should be limited to *probable, but not yet confirmed* regressions
[22:05] <bdmurray> hggdh: and my point is there is no idea for regression-potential as a tag as *probable* can be determined with tag + status or tag + target (release)
[22:05] <bdmurray> s/idea/need/ ;-)
[22:06] <drew212> hggdh: i got an error even with edge, should i turn off my automatic redirection?
[22:06] <hggdh> bdmurray: even better...
[22:06] <hggdh> drew212: yes, try without edge -- you will have to edit the URL, BTW. Edge has a more strict timeout
[22:07] <hggdh> jibel: I agree with bdmurray, we could just drop regression-potential
[22:07] <drew212> hggdh: well it doesnt work either way...
[22:07] <devildante> can someone triage bug 387247?
[22:07] <ubot2> Launchpad bug 387247 in update-manager (Ubuntu) (and 2 other projects) "implement launchpad changelog in update-manager (affects: 1) (heat: 15)" [Undecided,Confirmed] https://launchpad.net/bugs/387247
[22:07] <hggdh> drew212: best bet, then, is #launchpad
[22:07] <bdmurray> drew212: what are your search parameters?
[22:07] <maco> yeah
[22:08] <jibel> and use the statuses to know if it's confirmed or not ?
[22:08] <drew212> bdmurray: i'm in ubuntu, searching for "firefox" under search for a package
[22:08] <hggdh> devildante: done
[22:09] <devildante> hggdh: thanks :)
[22:09] <jibel> hggdh, so the workflow would be. I, as a reporter, file a bug which I think is a regression.
[22:09] <jibel> I, or a triager,  tag it as regression-release and set the status to new.
[22:10] <bdmurray> drew212: okay #launchpad - if you want a workaround let me know what you want to find
[22:10] <jibel> if the regression is confirmed, the triager nominate for that release and set the status to confirmed/triaged if there is enough information
[22:10] <hggdh> jibel: sounds like it, yes
[22:10] <drew212> bdmurray: go to #launchpad?
[22:11] <bdmurray> drew212: yeah, sorry
[22:11] <jibel> and if the regression if fixed in the dev release, the main task is closed as fixed release.
[22:11] <hggdh> yes
[22:11] <bdmurray> jibel: yes and yes
[22:11] <maco> devildante: i marked it wishlist too
[22:11] <hggdh> if the bug is not fixed during dev, it stays correctly set
[22:11] <micahg> well, if you get rid of regression-potential, you'll have to have a task for the dev release as well
[22:11] <devildante> thank you, maco! ;)
[22:12] <micahg> which can cause issues if it's not fixed by the next release
[22:12] <hggdh> maco: thank you (I forgot)
[22:12] <jibel> hggdh, bdmurray, and we use the -updates and -proposed to identify the pocket.
[22:12] <bdmurray> jibel: right which is the same as now
[22:12] <bdmurray> micahg: cause issues how?
[22:12] <jibel> hggdh, bdmurray, sounds good.
[22:12] <hggdh> +1
[22:12] <micahg> bdmurray: you need a new task added for each new release it's not fixed in
[22:12] <hggdh> yes
[22:13] <hggdh> but it is better than currently is (regression-potential bugs on released versions, no tasks
[22:13] <bdmurray> micahg: yes and that is correct - the regression should be tracked on a per release basis
[22:13] <jibel> bdmurray, hggdh, this will only need a status check after each release. But that's a good target for a bug day.
[22:13] <hggdh> jibel: I agree. We will have to spread the news when we go this way
[22:13] <dyfet> bug #625996 could be marked triaged
[22:13] <ubot2> Launchpad bug 625996 in clamtk (Ubuntu) "ClamAV antivirus engine requires updating (affects: 1) (heat: 3440)" [Undecided,New] https://launchpad.net/bugs/625996
[22:15] <jibel> bdmurray, hggdh, there will have only one thing to sort ... all the reports filed by apport against linux and tagged release-potential without human intervention.
[22:16] <bdmurray> jibel: /usr/share/apport/package-hooks/source_linux.py
[22:17] <micahg> hggdh: was using regression-$RELEASE to make it easily searchable already discussed?
[22:18] <bdmurray> jibel: and I imagine the kernel bug janitor could update existing tags as it processes bugs
[22:18] <hggdh> micahg: no, it has not. I am sort of not really happy with this option, though -- it gets old fast (regression-karmic, for example, and still a regression today)
[22:18] <micahg> hggdh: well, tags are less noisy tahan bugs especially if they don't get done
[22:19] <jibel> bdmurray, yes I imagine that too but that needs to be discussed with the kernel team. I don't know much about their workflow regarding those reports. Most of them looks the same to me.
[22:19] <hggdh> bdmurray, jibel ^
[22:19] <micahg> s/bugs/tasks/
[22:19] <bdmurray> micahg: I also feel that it places too much work on the reporter / early triager
[22:19] <bdmurray> jibel: I'd be happy to handle talking to them
[22:19] <micahg> bdmurray: to mark regression-$RELEASE_REPORTED?
[22:20] <micahg> rather than needing a dev to add a task?
[22:20] <jibel> micahg, and the tags will carry to much information. It's only a marker, not a placeholder to add useful bug information.
[22:20] <bdmurray> micahg: yes and I have plans to fix the latter issue. ;-)
[22:20] <micahg> bdmurray: super task creation script?
[22:21] <bdmurray> no changes to Launchpad ;-)
[22:21] <micahg> bdmurray: for bug supervisor?
[22:22] <bdmurray> micahg: Release Manager which would likely include some bug supervisor members
[22:22] <micahg> bdmurray: you want to restrict task creation further?
[22:22] <bdmurray> micahg: can you target a bug to a release?
[22:23] <micahg> bdmurray: no, MOTU can do universe and core-dev everything AFAIK
[22:23] <bdmurray> micahg: last I checked that was for setting milestones not release targetting
[22:23] <micahg> bdmurray: no, bug supervisor can assign milestones
[22:24] <yofel> I can set a milestone, so every BC member should be able to do that
[22:27] <bdmurray> okay right - so bug supervisor approve nominations and release manager set milestone
[22:28] <micahg> bdmurray: bug supervisor cam set milestones on bugs
[22:28] <bdmurray> micahg: right and I think that is wrong
[22:28] <bdmurray> It hasn't been an issue yet but milestones should be up to the release team
[22:28] <dyfet> and bug #622919
[22:28] <ubot2> Launchpad bug 622919 in ubuntu "Missing autostart directory (affects: 1) (heat: 577)" [Undecided,New] https://launchpad.net/bugs/622919
[22:29] <micahg> bdmurray: approving nominations requires knowledge of the SRU process and should have some understanding of the change required ( I think it's quite appropriate to have a dev do it)
[22:29] <micahg> bdmurray: I agree on the milestoning though
[22:29] <hggdh> dyfet: 'ubuntu' is the wrong package on this bug
[22:30] <dyfet> ah...good point
[22:30] <jibel> sbeattie, was your system hit by bug 614993 upgraded from a previous release already (I mean previous to lucid) ?
[22:30] <ubot2> Launchpad bug 614993 in xorg-server (Ubuntu) (and 1 other project) "10.04 -> 10.10 upgrade fails: pkgProblemResolver::Resolve generated breaks: xserver-xorg-video-v4l demoted to universe (affects: 13) (dups: 8) (heat: 103)" [Critical,In progress] https://launchpad.net/bugs/614993
[22:30] <bdmurray> jibel: I saw that yesterday too
[22:31] <jibel> bdmurray, we've fixed upgrade another issue but I'm enable to reproduce that one on a fresh lucid.
[22:32] <bdmurray> jibel: mines been upgraded since feisty or edgy. ;-)
[22:32] <jibel> bdmurray, and all the status files I analyzed contains package from older release that do not exist anymore in lucid.
[22:33] <jibel> bdmurray, is your system using some nvidia/nouveau driver ?
[22:34] <bdmurray> jibel: no, ati
[22:35] <jibel> bdmurray, which driver ?
[22:36] <micahg> bdmurray: devs should be able to nominate milestones or something if it becomes limited to release managers
[22:37] <bdmurray> jibel: radeon
[22:38] <jibel> bdmurray, no fglrx package installed at all ?
[22:39] <bdmurray> jibel: ii  fglrx-modaliases                                  2:8.762-0ubuntu0sarvatt~lucid                   Identifiers supported by the ATI graphics dr...
[22:42] <jibel> bdmurray,  bah, It seems that you're not using a package from an official Ubuntu repository, because of this we cannot fix your particular bug ;)
[22:44] <bdmurray> jibel: heh, okay ;-)
[22:48] <jibel> bdmurray, is xserver-xorg-radeonhd installed, if so, please remove it and tell me if you can upgrade ?
[22:50] <bdmurray> jibel: and leave fglrx-modaliases alone?
[22:50] <jibel> bdmurray, yes leave it alone.
[22:51] <jibel> bdmurray,the full name is xserver-xorg-video-radeonhd
[22:51] <bdmurray> jibel: yes, I found it
[22:51] <bdmurray> jibel: still could not calculate the upgrade
[22:52] <jibel> bdmurray, :/ I've been able to reproduce the pb with that one, there must be another video driver which have been removed in maverick.
[22:54] <jibel> bdmurray, please pastebin the output of dpkg -l "xserver-xorg-video*"|grep ^ii
[22:55] <bdmurray> http://pastebin.ubuntu.com/486037/
[22:57] <sbeattie> jibel: yes, I think it's roughly been upgraded all the way up from hardy.
[22:58] <jibel> sbeattie, can you try removing xserver-xorg-video-radeonhd and tell if it helps ?
[22:58] <sbeattie> jibel: trying.
[23:01] <dyfet> And I think bug #619621 can be marked as triaged.  I can make a patch for us and debian based on this report.
[23:01] <ubot2> Launchpad bug 619621 in gnomeradio (Ubuntu) "some errors in source (affects: 1) (heat: 293)" [Undecided,New] https://launchpad.net/bugs/619621
[23:04] <yofel> jibel: do you know if anyone is looking into those 'is already installed and configured' bugs? we get a lot of them these days
[23:04] <jibel> bdmurray, no luck.
[23:05] <yofel> dyfet: if you plan on fixing the bug, please set the status to in progress and assign the bug to you
[23:05] <jibel> bdmurray, I installed them all and the system still upgrades.
[23:05] <dyfet> yofel, okay
[23:06] <sbeattie> jibel: wooo, seems to be able to calculate an upgrade path now.
[23:06] <jibel> sbeattie, cool \o/
[23:11] <jibel> yofel, yes and no. We know that this bug exists but not what is causing it and how to reproduce it.
[23:13] <jibel> yofel, I've been working on it with mvo, and we think that a system crash is the cause. And that following that crash the apt binary cache and dpkg status database become out of sync.
[23:13] <jibel> yofel, but the error is harmless so we've not been very far.
[23:14] <yofel> ok thanks (I tend to agree about the cause)
[23:14] <devildante> can someone triage bug 433972?
[23:14] <ubot2> Launchpad bug 433972 in linux (Ubuntu) (and 1 other project) "Internet ping is very slow (affects: 31) (heat: 159)" [Undecided,Confirmed] https://launchpad.net/bugs/433972
[23:17] <yofel> devildante: any proposed importance?
[23:17] <devildante> yofel: medium
[23:20] <yofel> JFo: ^
[23:20] <jibel> time to go to bed, good night all!
[23:20] <yofel> I won't touch the bug for now as the last person there isn't the original reporter and there are many that claim to have the same issue
[23:21] <yofel> for kernel bugs every one of them should file their own bug though
[23:21] <yofel> not sure how the kernel team handles that
[23:44] <devildante> yofel: okay :)
[23:46] <yofel> devildante: bug control app question 3: we mostly want to make sure you have read the documentation, as the triage guide has a section on apport crashes
[23:46] <yofel> https://wiki.ubuntu.com/Bugs/HowToTriage#Apport%20crash%20reports
[23:49] <dyfet> I think bug #616274 can be marked as triaged, at least there is enough info for someone to decide what they want to do with it :)
[23:49] <ubot2> Launchpad bug 616274 in gparted (Ubuntu) "gparted menu entry depends on gksu (affects: 1) (heat: 253)" [Undecided,New] https://launchpad.net/bugs/616274