| 29 Jun 2022 |
 gotmax (He/Him) | Re the Stalled Request Policy, I think we just need to clarify the language | 19:56:14 |
 tdawson | Yep, looking at it, I can see where we can clarify it. | 19:56:52 |
| gotmax (He/Him) | smooge: https://bugzilla.redhat.com/show_bug.cgi?id=2100618#c2 | 19:57:26 |
| gotmax (He/Him) | We're waiting for the RHEL go-rpm-macros maintainers to fix it. | 19:57:51 |
 smooge | lovely.. I need to get this fixed myself asap | 19:58:46 |
| gotmax (He/Him) | I might be able to submit a temporary to epel-rpm-macro's overrides to fix it | 19:58:51 |
| smooge | ha.. my problem is the fact that my depth of despair started with a package not finding golist and so I started rebuilding the world to get it | 19:59:36 |
| gotmax (He/Him) | Speaking of which, I'm still waiting for my other epel-rpm-macros PR to get merged | 19:59:49 |
| smooge | so I guess I need some sort of temporary fix macro rpm which puts this in | 19:59:58 |
| gotmax (He/Him) | I can submit try to do that. I'm pretty familiar with the go macros. | 20:00:49 |
| gotmax (He/Him) | * I can try to do that. I'm pretty familiar with the go macros. | 20:01:21 |
| smooge | so I am trying that patch in the https://gitlab.com/redhat/centos-stream/rpms/go-rpm-macros/-/merge_requests/10 list and it doesn't seem to help | 20:43:10 |
 carlwgeorge | tdawson: regarding the extra step to clear a needsinfo, in case you haven't seen it, when that flag is set on you and you comment on a bug, there is a checkbox that says something like "i'm providing the needed info to clear the flag". it's worked well enough for me that i don't mind the needsinfo step. | 20:45:28 |
| gotmax (He/Him) | smooge: I'll look at it. You might be having a different problem | 20:49:45 |
| gotmax (He/Him) | smooge: I'll look at it later. You might be having a different problem. | 20:50:16 |
| smooge | gotmax (He/Him), I found the problem and fixed it in the patch | 20:50:45 |
| smooge | well maybe | 20:50:55 |
| smooge | nope I have created another problem | 20:51:03 |
 nirik | perhaps it's just me, but I think of needinfo as being "I need information from X and it's urgent/important, you need to answer outside the normal workflow of answering bugs so it can unblock something' | 20:51:06 |
| smooge | for a lot of packagers I have dealt with.. the only way they ever seem to see a bug or answer is when you finally move it to NEEDINFO | 20:53:45 |
| smooge | I don't know if it its some filtering on their part.. but you can spend weeks not getting anything.. and then flip the tag and 'oh sorry didn't see this' | 20:54:26 |
| smooge | gotmax (He/Him), I fixed the patch so it 'works' now. | 21:00:58 |
| tdawson | The thing is that I don't go back to the bug and comment on it. When I get permissions, I branch, then build, then update and I let bodhi do all the work. | 21:01:19 |
| smooge | so much boiling the ocean to get this working | 21:01:22 |
| tdawson | So when I have 8 or 15 packages that I do that to, going back and putting a comment on each one, just to clear a tag ... it takes time. | 21:02:33 |
| smooge | yeah understood | 21:03:21 |
 Michel Alexandre Salim 🎩 | I always clear the NEEDINFO when I create the branch, FWIW. assign to self, paste the link to the branch request ticket, clear needinfo, save | 21:32:49 |
| Michel Alexandre Salim 🎩 | In reply to @tdawson:libera.chat
The thing is that I don't go back to the bug and comment on it. When I get permissions, I branch, then build, then update and I let bodhi do all the work. ahh | 21:33:01 |
| Michel Alexandre Salim 🎩 | yeah, I wonder if it should be automated | 21:33:06 |
| Michel Alexandre Salim 🎩 | (sorry, Matrix just started catching up on the conversation as I reopened my laptop) | 21:33:23 |
