=== lukedashjr is now known as luke-jr === jose_ is now known as jose [15:27] what's the preferred way to request deletion/redacting a bug? a user reported a bug to one of our projects and accidentally included some information in it they wanted kept private. they've edited the description but of course the detail is still there in the original description/activity log views. thankfully it was reported as a private bug, but i don't want to end up leaving it private forever so [15:27] curious what the best solution is [15:28] fungi: support link in the topic if you can describe the issue to us without repeating private information, otherwise email feedback@launchpad.net === cjwatson changed the topic of #launchpad to: Help contact: guruprasad (05:00-13:00 UTC Mon-Fri) | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide https://help.launchpad.net/ | Support and spam reporting: https://answers.launchpad.net/launchpad === cjwatson changed the topic of #launchpad to: Help contact: guruprasad (05:00-13:00 UTC Mon-Fri) | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support and spam reporting: https://answers.launchpad.net/launchpad [15:29] sounds good. since the bug is private it's probably safe for me to mention the bug number in the support request [15:30] thanks! [15:30] fungi: it's a bit fiddly and involves SQL surgery, but we do have a way to "promote" an edited version of a bug's description to pretend as though it's the original description [15:30] I've done it like twice before, that means it's a process, right? [15:31] sure, i mean completely deleting the report would be fine too, the reporter is willing to submit a new sanitized version [15:31] "completely deleting" would amount to moving it to a different private project with more limited visibility, which probably isn't better [15:31] is one easier or more possible than the other? [15:31] got it [15:31] thanks again! [15:32] happy for us to do the promote-to-original thing, probably, though will need to look at the details [15:34] cjwatson: https://answers.launchpad.net/launchpad/+question/703908 [15:35] and apologies for the hassle. i'm unfortunately all too familiar with having to perform similar tasks for users [15:42] hello, I noticed two spam messages/accounts - https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1779432/comments/62 and https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1779432/comments/63 [15:42] -ubottu:#launchpad- Launchpad bug 1779432 in LibreOffice "[upstream] Libre Writer doesn't do duplex printing" [High, Confirmed] [15:51] ricotz: could you file a ticket for those using the support link in the topic please? [15:51] can't do it right now, I just started a deployment on my laptop and everything is running like treacle [15:52] cjwatson, done [15:52] https://answers.launchpad.net/launchpad/+question/703909