-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
net-p2p/qbittorrent: add 4.6.3 #34917
Conversation
Signed-off-by: David Roman <davidroman96@gmail.com>
The referenced issue was fixed in 4.6.1 Closes: https://bugs.gentoo.org/917165 Signed-off-by: David Roman <davidroman96@gmail.com>
Signed-off-by: David Roman <davidroman96@gmail.com>
Pull Request assignmentSubmitter: @stkw0 net-p2p/qbittorrent: @gentoo/proxy-maint (maintainer needed) Linked bugsBugs linked: 917165 In order to force reassignment and/or bug reference scan, please append Docs: Code of Conduct ● Copyright policy (expl.) ● Devmanual ● GitHub PRs ● Proxy-maint guide |
Pull request CI reportReport generated at: 2024-01-20 13:43 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
See also #34949. I'm inclined to merge the other one as yours would be easier to then rebase. |
I see. Then I will close this PR as this was mostly superseded by the other one. btw bug https://bugs.gentoo.org/917165 should be closed I think, given that the ebuild containing the issue has been removed from the tree. |
You're still free to adopt the package with Eli though. |
Thanks. Maybe in a future I will. If the other person is already active we would need to coordinate to avoid making two times the same PR, etc. So, for now I think it's easier to let the other maintainer take care of it. |
Hmm, really that bug report should have been closed when 4.6.1 was added to the tree on the grounds that it was fixed at that time. The existence of an older ebuild with the bug still there doesn't mean the bug wasn't fixed. :) |
I think that, if an older ebuild has a known issue that can be hit by a user, makes sense to keep the bug open (even more if the ebuild references a specific version). Obviously, it would be better to fix the ebuild or drop it instead of keeping a buggy version when a new one doesn't has that problem. |
Also: