[09:37] <ari-tczew> Unit193: The fix for lightdm-gtk-greeter (B-D on libido) has been uploaded.
[14:09] <rubund> Hi, If a bug report contains several bugs, and I create a patch which fixes one of them. How should I proceed? Is it necessary to split the bug report by creating new reports for every one of them?
[14:27] <cjwatson> It's generally best for a bug report not to contain multiple actionable items.
[14:27] <cjwatson> Though it can reasonably enough be a single thing that needs fixes in multiple places before it's properly fixed.
[14:27] <cjwatson> But if it's genuinely several disconnected problems, then I would split it.
[14:28] <rubund> ok, and how would it then be linked back to the original bug report ?
[14:29] <rubund> since the importancy will not be reflected by the new bug reports
[14:29] <rubund> duplicate?
[14:29] <cjwatson> Just put links to the new one in comments on the old one, and set the importance etc. of the new one as appropriate.
[14:30] <rubund> ok, thank you very much
[14:30] <cjwatson> You can only have one duplicate target so that doesn't really work.  I'd just close whatever's left of the old one with references to the split bugs.
[14:30] <cjwatson> Unfortunately Launchpad doesn't have a "clone" operation on bugs.
[14:34] <rubund> ok. So the bug I'm talking about is this one: (LP: 1315149). It basically just says that the package is unusable in trusty. Some of the things have already been fixed upstream and should probably go into trusty quite soon, while others are harder to fix (won't fix, not so important). I believe I just should create a new bug report with a more specific title if I fix parts of it then.
[14:34] <cjwatson> I have to go now so don't have time to look in any detail, I'm afraid.
[14:35] <cjwatson> It's understandable that bug submitters can't always get things at the right granularity; sometimes it takes more understanding of the pieces involved to do so.
[14:35] <rubund> that's fine, thanks for the help. It's clear for me now I guess
[14:35] <rubund> have a nice day !
[16:55] <shnatsel> Hello everyone! I see libdee received important fixes back in 2013 (e.g. https://bugs.launchpad.net/dee/+bug/1246263), and while Ubuntu ships packages with the fixes applied, there was no upstream release with them. I'm looking to package an updated libdee for Debian, and I obviously need these fixes, and it seems it would be much easier for everyone to just make an upstream release with them. Whom should I contact to request an upstream release?
[21:14] <ari-tczew> Noskcaj: about bug 1334185, have you tested that package? I guess whether it works fine with upower 0.9.23