[00:20] <jmburgess> is bughelper no longer in the repository?
[00:26] <jmburgess> it seems lit it isn't
[03:03] <geofft> Hm. Can I not reopen a Fix Released bug? Should I just file a new one?
[10:09] <evfool> hggdh, mvo: about bug 199669 - it's triaged for both update-manager and update-notifier in Ubuntu, could you explain what needs to be done in update-manager?
[10:09] <ubot4> Launchpad bug 199669 in update-notifier (Ubuntu) (and 3 other projects) "Tray notification doesn't disappear when the Update Manager starts (heat: 2)" [Wishlist,Triaged] https://launchpad.net/bugs/199669
[10:17] <mvo> evfool: its only a issue for poeple using the non auto-open mode (which is not the default on ubuntu anymore)
[10:21] <evfool> mvo: but what needs to be done in u-m to fix it? isn't it only an update-notifier bug?
[10:23] <mvo> evfool: u-m could send a dbus signal, but I guess all the u-n should do is what the bus and if u-m appears just hide, so you are right, nothing for update-manager to do here and its fine to close the task
[10:24] <evfool> mvo: thanks, setting it to invalid then
[10:25] <mvo> thanks! please include the note about the bus watching that u-n needs to do
[13:50] <veger> hallo, anyone around to answer a couple of questions?
[14:19] <hggdh> veger: there is always someone around; it is better to just ask the questions, and whoever knows the answer will (eventually) answer them
[14:21] <veger> tried that yesterday (and fialed) ;)
[14:21] <veger> *failed
[14:22] <veger> I found an upstream report for bug 818775, stating that it has a  wishlist importance. So could someone set the LP report to Wishlist importance as well?
[14:22] <ubot4> Launchpad bug 818775 in kdeutils (Ubuntu) (and 1 other project) "Ark: adding a file to a folder get it in the 'root' of the archive (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/818775
[14:23] <veger> Furthermore, I suppose I should set the status of the bug report to Triaged?
[14:34] <kamusin> veger, I have already done this for you ;)
[14:34] <veger> thanks
[14:35] <veger> as I'd like to learn: I had the correct ideas for setting it to wishlist due to the wishlist status of the upstream report?
[14:36] <paultag> veger: not in all cases, there might be some cases where something we see as critical ( a use case we have ), that upstream does not care about
[14:37] <paultag> veger: so if upstream only cares about, say, fedora, and we are having a critical issue because it interfaces with package X we use by default in Ubuntu that say fedora does not have, we might consider it critical, but upstream might consider it minor / wishlist
[14:37] <veger> So for such cases I'd need info on 'us'? :)
[14:37] <paultag> veger: that case is very very rare :)
[14:37] <paultag> veger: :)
[14:38] <veger> thanks for helping
[14:38] <paultag> sure sure
[14:38] <yofel> hm...
[14:39] <yofel> I'm closing this. We (the kubuntu team) don't track any upstream issues that aren't at least High/Critical on launchpad. We only end up with bug zombies for long fixed bugs
[14:40] <paultag> yofel: someone should write an lplib script to clear out upstream fixed bugs
[14:40] <paultag> yofel: it could be useful if someone wants to help and they cherry pick some low hanging fruit
[14:41] <paultag> not telling you that policy's out of line, I agree that happens, but I'm just shooting up an idea
[14:41] <veger> oh... so after sending a report upstream it can be closed...? (assuming it is a low importance bug)
[14:41] <paultag> veger: no, so after upstream closes, it will close the local bug too with a message
[14:41] <yofel> the script would be an idea, the cherry picking not really since we don't add patches unless it's really necessary
[14:41] <paultag> veger: yeah but even something like me subscribing to a bug
[14:42] <yofel> and then the bug would be at least High anyway
[14:42] <paultag> veger: it's be nice to get followup :)
[14:42] <paultag> not nitpicking or anything
[14:42] <yofel> veger: that's for kde packages, usually triaged is right
[14:43] <veger> yofel: well I kind of try to help out with kde packages... but I'll try to rember it is for kde only :)
[14:43] <yofel> feel free to poke in #kubuntu-devel for details, haven't triaged much myself lately :/
[14:45] <veger> As I mentions I have multiple questions: bug 577560 is fixed upstream with a patch. I have updated the package and tried it. It works and solves the problem. Should I set the status to 'fix committed'? And should I do anything else to make sure the patch ends up in the kubuntu repositories?
[14:45] <ubot4> Launchpad bug 577560 in plasma-widget-networkmanagement (Ubuntu) (and 1 other project) "can't connect to WPA2 Entreprise using PEAP and MSCHAPv2 (affects: 7) (heat: 40)" [Undecided,Confirmed] https://launchpad.net/bugs/577560
[14:51] <yofel> veger: that bug should be fix released, as the snapshot in oneiric (from the nm09 branch) was taken after the fix was committed.
[14:52] <yofel> as for natty and earlier the fix needs to follow the SRU procedure
[14:55] <veger> I try to find the nm09 branch, is it this onehttps://code.launchpad.net/~ubuntu-branches/ubuntu/oneiric/plasma-widget-networkmanagement/oneiric ?
[14:56] <veger> I'll read up on the SRU procedures now...
[14:59] <yofel> veger: a) the nm09 branch won't work in Natty b) the SRU procedure requires minimal patches that fix the issue, so you can't just SRU a new snapshot
[15:02] <veger> yes, I read about the requirements for a SRU
[15:03] <veger> I'll set the bug to fix released and leave it (no updates for natty... :( ;) )
[15:03] <yofel> I looked at that bug a few days ago actually, less than trivial SRU since the upstream patch doesn't apply on the natty package
[15:04] <veger> I tried yes, and I ended up with grabbing a snapshot
[15:05] <veger> Quite a lot of (academic) users have problems due to this bug
[15:06] <veger> for my personal understanding, were can I find the nm09 branch? So I can find it a next time in order to see whether a fix is provided or not?
[15:09] <yofel> veger: 'git clone git://anongit.kde.org/networkmanagement' -> 'git checkout nm09' or look at http://quickgit.kde.org/?p=networkmanagement.git&a=shortlog&h=refs/heads/nm09
[15:12] <yofel> veger: for the upstream one, launchpad will have whatever we have in the archive
[15:15] <veger> yofel: thanks for the info!
[15:16] <veger> http://quickgit.kde.org/ will become my friend :)
[15:23] <veger> There are quite some related reports (mostly for different encryption types), but all due to the same problem supposedly. bug 507835 is such an example, but here there is a user asking whether it is possible to backport the change for natty. Should I tell him 'no'?
[15:23] <ubot4> Launchpad bug 507835 in plasma-widget-networkmanagement (Ubuntu) "Can't connect to WPA enterprise (LEAP) (affects: 3) (heat: 21)" [Undecided,Invalid] https://launchpad.net/bugs/507835
[15:39] <veger> I have replied on the mentioned bug, I think it is a good reply... :)
[15:41] <veger> in bug 660970, it is mentioned that the problem is fixed in 'the current release', so it is unknown how it was fixed (for me). As I rembember the bug should be closed as Invalid, right?
[15:41] <ubot4> Launchpad bug 660970 in evolution (Ubuntu) "Mark messages as read in current folder and subfolders doesn't work (affects: 2) (heat: 17)" [Undecided,Incomplete] https://launchpad.net/bugs/660970
[15:43] <yofel> veger: why no? it's just that nobody did it yet
[15:46] <veger> yofel: Just to be sure I rembered correctly...
[15:49] <veger> and my last question (for now), bug 698035 tells that the --help output is incomeplete. I think it is just being short and that the use should read the manual pages for the complete help. How should I handle this?
[15:49] <ubot4> Launchpad bug 698035 in evolution (Ubuntu) "evolution --help talks unhelpfully about "the specified component" (affects: 1) (heat: 20)" [Undecided,New] https://launchpad.net/bugs/698035
[16:51] <jmburgess> Is the bughelper package no longer in natty?
[16:53]  * yofel thinks we junked that a long time ago
[16:53] <yofel> what do you want to use it for?
[16:54] <jmburgess> Oh I just saw it was good for finding duplicates and such
[16:54] <jmburgess> And then doing bug patterns
[16:55] <micahg> jmburgess: take a look at bughugger
[16:55] <yofel> well, the LP ui is usable these days, if you need a more usable search go to google and use 'site:bugs.launchpad.net <searchterm>'
[16:55] <RedSingularity> jibel: any idea what this is?  :  /tmp/update-manager-XRc3zk/DistUpgradeCache.py:729: DeprecationWarning: Attribute 'Essential' of the 'apt_pkg.Package' object is deprecated, use 'essential' instead.
[16:56] <jmburgess> Can launchpad search attachments as well?
[16:56] <jibel> RedSingularity, that's a deprecation warning :)
[16:56] <RedSingularity> jibel: I have seen that a few times.  What does it mean exactly?
[17:00] <jibel> RedSingularity, it means that the code must be updated to the latest api. Is that on oneiric, it changed a while ago IIRC.
[17:01] <RedSingularity> jibel: looks like an upgrade from natty to oneiric.  That code is at the bottom of the apt.log
[17:06] <RedSingularity> jibel: I was trying to track down the culprit package.  Have a look at the log.  bug 798512
[17:06] <ubot4> Launchpad bug 798512 in update-manager (Ubuntu) "Upgrading Kubuntu to version 11.04 error at the second process (affects: 1) (heat: 8)" [Undecided,Incomplete] https://launchpad.net/bugs/798512
[17:10] <RedSingularity> jibel: I had thought python-kde4 may have been it but that package seems fine....
[17:24] <jmburges> Bug 565543 can be marked as triaged I think. Importance medium
[17:24] <ubot4> Launchpad bug 565543 in linux (Ubuntu) (and 1 other project) "Alps touchpad detected as ImPS/2 Generic Wheel Mouse(in VAIO E series) after the kernel upgrade (affects: 68) (dups: 1) (heat: 404)" [Medium,Confirmed] https://launchpad.net/bugs/565543
[20:25] <kamusin> eeebotu is gone hggdh :(
[20:25] <hggdh> kamusin: checking, thanks
[20:26] <kamusin> you are welcome ;)
[20:28] <hggdh> kamusin: recovered, thanks for the heads up