-
Notifications
You must be signed in to change notification settings - Fork 7
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
NMU: terminal-size patch #310
Comments
Can this move forward? |
ping This blocks ghcup from being uploaded to hackage, btw. |
@hasufell |
|
@phadej GHC manual is also incorrect in this case: http://downloads.haskell.org/ghc/9.2.1-rc1/docs/html/users_guide/exts/ffi.html#the-capi-calling-convention I agree that from practical viewpoint it is fine, but I'd like to exhaust other possible options before going for NMU. |
The patch itself is not good enough for NMU, at least
|
@Bodigrim the policy requires us (= Trustees) to contact the maintainer too. And wait some time so they (hopefully) reply. Addition: that step is non-commiting anything: Step 3 in https://github.com/haskell-infra/hackage-trustees/blob/master/policy.md#policyprocedure-2
|
Btw, terminal-size is not buildable with That's one problem @bgamari could solve. |
Not interested. I'll probably just fork the modules into my own repo. |
So what's the reason this isn't fixed? Due to the lack of action here I've already forked it into my own repos, so my projects aren't blocked from being used on hackage. Regardless, this bug may break other peoples packages. |
@hasufell The reason is that Hackage Trustee are not "maintainers of everything" and are foremost responsible to exclude unbuildable configurations by manipulating package bounds. NMUs are extremely rare and mostly limited to mechanical migration of impactful packages to newer versions of dependencies. Generally speaking, we have no expertise or domain knowledge to approve bug fixes, especially of subtle nature, as the PR in question. That's why I am not comfortable to undertake a NMU in this case. Other Trustees may be of different opinions. |
What? You're part of CLC. The bug was reported by a GHC developer, who's extremely knowledgeable about C API and published a blog post about these sort of issues: https://www.haskell.org/ghc/blog/20210709-capi-usage.html |
I double checked and the point about nmu procedure is that it is for trustees to fix version bump induced issues: https://github.com/haskell-infra/hackage-trustees/blob/master/policy.md#3-source-changes-simple-patches Fixing other bugs is not in the purview of people as trustees and not in the purview of the nmu process. Afaik the only approved process we have for fixing bugs that are not simply version bump induced breakages is a package takeover (which can mean being added as a maintainer, rather than simply kicking out the prior maintainer). Thanks for pushing for clarity on this, and my apologies for not paying attention and trying to clear this up sooner. I'm going to close this for now -- acting on stuff like this will go beyond what the role of trustees is supposed to be and set precedents that could cause more confusion in the future. |
Thanks for the clarification... the wording is a bit implicit. Maybe it should be clarified. |
biegunka/terminal-size#16
@bgamari
The text was updated successfully, but these errors were encountered: