On 04/08/2020 15:08, Ken Brown via Cygwin-apps wrote:
On 7/21/2020 5:24 PM, Ken Brown via Cygwin-apps wrote:
This is a follow-up to
https://sourceware.org/pipermail/cygwin/2020-July/245623.html
As I explained there, a patch applied to the Cygwin build causes php
to often call mmap with MAP_FIXED, and some of these calls fail.
Removing the relevant hunk of the patch fixes the reported problem,
and I don't see any reason why that hunk should be needed.
Obviously Yaakov had a reason for applying that hunk, and I'm guessing
(hoping) that the reason is no longer applicable.
Ideally, someone should ITA php and deal with this. That person will
not be me. I don't use php and I know nothing about it. If no one
steps forward, I would be willing to do a one-time non-maintainer upload.
No one has stepped forward, and Yaakov hasn't responded to say why he
needed the problematic portion of the patch. In view of the recent post
on the cygwin list
https://sourceware.org/pipermail/cygwin/2020-August/245752.html
I think I should probably go ahead with an NMU. Any opinions?
As a practical matter, anyone who can change cygwin-pkg-maint could
upload anything, after jumping through sufficient hoops.
(In the interest of making life easier for those people, calm doesn't
usually require them to jump through those hoops (see [1]), allowing
them to:
- upload orphaned packages
- push to any packaging repository
[1] https://cygwin.com/pipermail/cygwin-apps/2020-February/039819.html)
> Jon, are you now the de facto packaging czar who can authorize this?
No, I don't think so.
My perspective is that, by virtue of having the necessary access and
being trusted to use it sensibly, you are already authorized.
Thanks for looking into this issue.
