public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: Fix for php
Date: Tue, 4 Aug 2020 16:07:41 +0100	[thread overview]
Message-ID: <3df647f8-6cac-4baf-4787-72c817dfc574@dronecode.org.uk> (raw)
In-Reply-To: <7ffa5319-b52a-d452-98c8-2acb9dffbec7@cornell.edu>

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.

      reply	other threads:[~2020-08-04 15:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 21:24 Ken Brown
2020-08-04 14:08 ` Ken Brown
2020-08-04 15:07   ` Jon Turney [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3df647f8-6cac-4baf-4787-72c817dfc574@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).