=== cpaelzer_ is now known as cpaelzer === scoobydoo_ is now known as scoobydoo [16:58] cpaelzer: hey! Any ideas on why https://bugs.launchpad.net/ubuntu/+source/postgresql-12 does not show https://bugs.launchpad.net/ubuntu/+source/postgresql-14/+bug/1996770 ? [16:58] -ubottu:#ubuntu-server- Launchpad bug 1996770 in postgresql-12 (Ubuntu Focal) "New upstream microreleases 10.23, 12.13 and 14.6" [High, In Progress] [16:58] in #1996770 pg-12 ans pg-10 also show a lighter color [16:58] :| [16:59] Cc sergiodj [17:52] athos: bugs against a source package that are targeted to a specific release don't show up on those lists. (that makes it very easy to overlook them.) I'm afraid I don't know if there's a way to find them or not [18:03] Oh, I see! Thanks, sarnold! [18:06] athos: that's a pretty screwed up bug state :-/ [18:06] There's a bug in Launchpad that if you delete a bug task, it can't be readded. So in general we avoid deleting bug tasks and mark them Invalid instead. [18:07] even mangling the url doesn't get me there: https://bugs.launchpad.net/ubuntu/+source/postgresql-10/+bug/1996770 [18:07] -ubottu:#ubuntu-server- Launchpad bug 1996770 in postgresql-12 (Ubuntu Focal) "New upstream microreleases 10.23, 12.13 and 14.6" [High, In Progress] [18:07] Like sarnold said, by default the listings only show bugs that are open against the development release [18:07] it changes back to postgresql-14 [18:07] https://bugs.launchpad.net/ubuntu/focal/+source/postgresql-12 [18:07] That works [18:08] You have to know to ask for a specific release in the URL. [18:08] Normally you can also do an advanced search and include "Fix Released" or "Invalid" or whatever, but in this case those tasks have been deleted so I don't think that'll work. [19:19] I'm sure I've forgotten this "specific release" thing at least twice now. I know I've forgotten that it's a thing entirely a few times as well :) [20:10] athos: because I only added a task for postgresql-12 via LP commandline, but no one ever added the source package itself [20:11] athos: I added postgresql-12 (to demonstrate the case) and no it is no more greyed out