[13:47] <Elliria> Hey there, if a bug affects two packages and has been filed under one of them, do we create an identical bug report under the other package as well or just leave the one bug report in place and use that?
[13:52] <Jeremy31> Elliria: you should be able to add more affected packages on launchpad
[13:53] <Elliria> Ah, okay. I see two shortcuts. One says "Also affects project" and the other says "Also affects distribution/package" and I'm guessing I'd want the second one?
[13:54] <Jeremy31> yrd
[13:54] <Jeremy31> yes
[13:54] <Elliria> This is the bug, by the way. I just added a comment to it: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1971757
[13:56] <Elliria> When I click that, do I change "Source Package Name" (which is filled in with wslu automatically) to the gimp-help-en (which is the other affected package)?
[13:58] <Jeremy31> That should do it
[14:00] <Elliria> It's giving me this error: There is no package in Ubuntu named "gimp-help-en".
[14:02] <Jeremy31> Maybe just gimp-help
[14:02] <Elliria> And when I try adding gimp-help-en to the "Also affects project" option instead, I get this error: There is no project in Launchpad named "gimp-help-en". Please search for it as it may be registered with a different name.
[14:02] <Elliria> Okay, will try it.
[14:03] <Elliria> That worked. Whew. Thanks. Will the Gimp team read the comments, though, to realize that it's very specifically the gimp-help-en package that's pulling in wslu?
[14:03] <Jeremy31> Somebody will read it
[14:04] <Elliria> Okay, sounds good. I've subscribed, so I'll find out what happens. If you haven't experienced this bug, you might want to look at it real quick so you'll know what to do when it happens. Heh.