Re: [PHP-DEV] Windows PECL build machine died

2024-03-20 Thread Derick Rethans
Hi,

To revive this ancient thread. We have made some progress getting these 
builds made for Windows again.

Shivam has been working on an extension builder for Windows 
(https://github.com/php/php-windows-builder?tab=readme-ov-file#build-a-php-extension)
 
— GHA actions to build your DLLs on release.

He's tried that on Xdebug: 
https://github.com/shivammathur/xdebug/blob/master/.github/workflows/release.yml

This is still pre-release, so please don't rely on this yet!

We are also looking at buliding some specific PECL extensions for 
Windows, and uploading them to the downloads server.

PECL DLLs are no longer served from the windows.php.net server either, 
but instead from downloads.php.net/~windows : 
https://pecl.php.net/package/ssh2/1.3.1/windows

Uploading built DLLs to this server can not be done automatically due to 
2FA requirements, but we'll think on how to improve that.

cheers,
Derick



On Sun, 23 Apr 2023, Casper Langemeijer wrote:

> Nothing seems to happen on this front, and our Windows users like to move to 
> PHP 8.2 too.
> 
> The windows.php.net site states: "This is because the Windows PECL build 
> machine died, and the team is still working on the long term plan of building 
> DLLs for PECL extensions with a new CI process."
> 
> We are 1 year since the machine died. 6 month since the statement on the 
> website. From the point of view of our users nothing has changed, and are 
> questioning if the windows project is still alive.
> 
> I'd like to ask: Is re-inventing the building process really a smart thing to 
> do if it means we'll be out-of-service for more than a year?
> 
> "We're doing our best to finish that as soon as possible, and keep you up to 
> date."
> 
> I'm not questioning intentions, but I hate to think this is 'our best'. We 
> should at least have and share a more concrete plan, possibly share a rough 
> timeframe and share if we hit a blocking problem. If help is needed, we 
> should ask.
> 
> Greetings, Casper

-- 
https://derickrethans.nl | https://xdebug.org | https://dram.io

Author of Xdebug. Like it? Consider supporting me: https://xdebug.org/support
Host of PHP Internals News: https://phpinternals.news

mastodon: @derickr@phpc.social @xdebug@phpc.social
twitter: @derickr and @xdebug

Re: [PHP-DEV] Windows PECL build machine died

2023-04-23 Thread Matthew Weier O'Phinney
On Sun, Apr 23, 2023, 3:33 PM Casper Langemeijer 
wrote:

> Nothing seems to happen on this front, and our Windows users like to move
> to PHP 8.2 too.
>
> The windows.php.net site states: "This is because the Windows PECL build
> machine died, and the team is still working on the long term plan of
> building DLLs for PECL extensions with a new CI process."
>
> We are 1 year since the machine died. 6 month since the statement on the
> website. From the point of view of our users nothing has changed, and are
> questioning if the windows project is still alive.
>
> I'd like to ask: Is re-inventing the building process really a smart thing
> to do if it means we'll be out-of-service for more than a year?
>
> "We're doing our best to finish that as soon as possible, and keep you up
> to date."
>
> I'm not questioning intentions, but I hate to think this is 'our best'. We
> should at least have and share a more concrete plan, possibly share a rough
> timeframe and share if we hit a blocking problem. If help is needed, we
> should ask.
>

Just as an FYI, for anybody in this situation, we (Zend) are doing Windows
builds of PHP; these have an E2E testing pipeline they pass before release.
Current community-supported versions can be downloaded for free, and we
provide LTS versions commercially. We support around 60 PECL extensions as
well.

Install instructions here:
https://help.zend.com/zendphp/current/content/installation/windows_installation.htm

Supported extensions list:
https://help.zend.com/zendphp/current/content/installation/php_pecl%20extensions.htm



>


Re: [PHP-DEV] Windows PECL build machine died

2023-04-23 Thread Casper Langemeijer
Nothing seems to happen on this front, and our Windows users like to move to 
PHP 8.2 too.

The windows.php.net site states: "This is because the Windows PECL build 
machine died, and the team is still working on the long term plan of building 
DLLs for PECL extensions with a new CI process."

We are 1 year since the machine died. 6 month since the statement on the 
website. From the point of view of our users nothing has changed, and are 
questioning if the windows project is still alive.

I'd like to ask: Is re-inventing the building process really a smart thing to 
do if it means we'll be out-of-service for more than a year?

"We're doing our best to finish that as soon as possible, and keep you up to 
date."

I'm not questioning intentions, but I hate to think this is 'our best'. We 
should at least have and share a more concrete plan, possibly share a rough 
timeframe and share if we hit a blocking problem. If help is needed, we should 
ask.

Greetings, Casper

Re: [PHP-DEV] Windows PECL build machine died

2023-02-18 Thread Pierre Joye
Hello,

I wonder if we could not use on demand resources for the builds (like
windows gh actions) and use the normal distribution mirrors setup?

Pierre

On Fri, Feb 17, 2023, 8:10 PM JEDI_BC / Bruno CHALOPIN 
wrote:

> Hi
>
> On 11/07/2022 18:25, Christoph M. Becker wrote:
> > On 11.07.2022 at 17:41, Hans Henrik Bergan wrote:
> >
> >> Do you mean it is unlikely that Github Actions will suffice? because
> that
> >> would definitely be a great solution if it was possible/feasible .
> >
> > No.  It is only unlikely that automated uploads to window.php.net will
> > ever be possible using GH actions.
> >
> >> Anyway, with regards to "I don't think there are special requirements
> >> regarding the hardware", can you give a rough estimate on RAM/disk space
> >> requirements?
> >
> > The old machine had something like 4 or 8 GB RAM, and a 128 GB hard disk.
>
> Is there recent development about the situation of the windows pecl
> build machine ?
>
> How can we help ?
>
> Regards,
>
> Bruno CHALOPIN
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>
>


Re: [PHP-DEV] Windows PECL build machine died

2023-02-17 Thread JEDI_BC / Bruno CHALOPIN

Hi

On 11/07/2022 18:25, Christoph M. Becker wrote:

On 11.07.2022 at 17:41, Hans Henrik Bergan wrote:


Do you mean it is unlikely that Github Actions will suffice? because that
would definitely be a great solution if it was possible/feasible .


No.  It is only unlikely that automated uploads to window.php.net will
ever be possible using GH actions.


Anyway, with regards to "I don't think there are special requirements
regarding the hardware", can you give a rough estimate on RAM/disk space
requirements?


The old machine had something like 4 or 8 GB RAM, and a 128 GB hard disk.


Is there recent development about the situation of the windows pecl
build machine ?

How can we help ?

Regards,

Bruno CHALOPIN

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php



Re: [PHP-DEV] Windows PECL build machine died

2023-02-17 Thread JEDI_BC / Bruno CHALOPIN

Hi

On 11/07/2022 18:25, Christoph M. Becker wrote:

On 11.07.2022 at 17:41, Hans Henrik Bergan wrote:


Do you mean it is unlikely that Github Actions will suffice? because that
would definitely be a great solution if it was possible/feasible .


No.  It is only unlikely that automated uploads to window.php.net will
ever be possible using GH actions.


Anyway, with regards to "I don't think there are special requirements
regarding the hardware", can you give a rough estimate on RAM/disk space
requirements?


The old machine had something like 4 or 8 GB RAM, and a 128 GB hard disk.


Is there recent development about the situation of the windows pecl 
build machine ?


How can we help ?

Regards,

Bruno CHALOPIN

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php



Re: [PHP-DEV] Windows PECL build machine died

2022-07-22 Thread Hans Henrik Bergan
.. should have written "making the cpus run hotter and clock lower and
harming single-thread performance without significantly increasing total
throughput, sometimes even harming total throughput" - and making it harder
to see how much *actual* cpu is being used by a process (a process
seemingly using 50% of a physical core might actually be using near 100% of
a core, but you can't see it in htop because HT makes it look like
50%/the-ht-core-looks-ready-to-go-even-if-it-isn't) - comparatively AMD's
SMT seems to nearly always increase total throughput.

On Fri, 22 Jul 2022 at 23:56, Hans Henrik Bergan 
wrote:

> 10 days of radio silence? What's going on? anyway benchmarks (countsey of
> bench.sh ) of the server/bandwidth
>
>  A Bench.sh Script By Teddysun ---
>  Version: v2022-06-01
>  Usage  : wget -qO- bench.sh | bash
> --
>  CPU Model  : Intel(R) Xeon(R) CPU E7- 4870  @ 2.40GHz
>  CPU Cores  : 40 @ 2524.597 MHz
>  CPU Cache  : 30720 KB
>  AES-NI : Enabled
>  VM-x/AMD-V : Enabled
>  Total Disk : 393.6 GB (48.7 GB Used)
>  Total Mem  : 125.9 GB (12.0 GB Used)
>  Total Swap : 8.0 GB (0 Used)
>  System uptime  : 10 days, 2 hour 11 min
>  Load average   : 40.18, 40.10, 40.13
>  OS : Ubuntu 20.04.4 LTS
>  Arch   : x86_64 (64 Bit)
>  Kernel : 5.4.0-122-generic
>  TCP CC : cubic
>  Virtualization : Dedicated
>  Organization   : AS31798 DataCity
>  Location   : Kitchener / CA
>  Region : Ontario
> --
>  I/O Speed(1st run) : 812 MB/s
>  I/O Speed(2nd run) : 841 MB/s
>  I/O Speed(3rd run) : 821 MB/s
>  I/O Speed(average) : 824.7 MB/s
> --
>  Node NameUpload Speed  Download Speed  Latency
>  Speedtest.net941.15 Mbps   829.87 Mbps 3.09 ms
>  Los Angeles, US  937.01 Mbps   903.15 Mbps 64.21 ms
>  Dallas, US   941.23 Mbps   898.69 Mbps 36.36 ms
>  Montreal, CA 888.80 Mbps   916.91 Mbps 11.09 ms
>  Paris, FR886.36 Mbps   820.77 Mbps 90.50 ms
>  Amsterdam, NL854.88 Mbps   770.73 Mbps 98.16 ms
>  Shanghai, CN 426.16 Mbps   833.23 Mbps 216.21 ms
>  Nanjing, CN  439.53 Mbps   542.91 Mbps 198.60 ms
>  Seoul, KR465.37 Mbps   367.20 Mbps 216.88 ms
>  Singapore, SG417.93 Mbps   132.76 Mbps 212.71 ms
>  Tokyo, JP668.62 Mbps   676.35 Mbps 134.48 ms
> --
>  Finished in: 5 min 35 sec
>  Timestamp  : 2022-07-22 21:35:37 UTC
> --
>
> - it incorrectly says 393GB because of partitioning, it's actually 1TB
>
> - I've intentionally disabled Hyperthreading because... in my
> opinion/experience, hyperthreading implementations in older Intel CPUs
> often did more harm than good, making the cpus run hotter and clock lower,
> this is a (high-end) 2011 model. (I have the opposite experience with AMD
> SMT fwiw)
>
>
>
> On Thu, 14 Jul 2022 at 01:18, Hans Henrik Bergan 
> wrote:
>
>> Fwiw Chris Haas / vendiadvertising.com has reached out, they're willing
>> to sponsor raid(1) if my proposal is accepted.
>> Haas is reading this mailing list, but does not wish to participate/post
>> directly at present.
>> (I have no prior relation, never heard of them before today)
>>
>> On Tue, 12 Jul 2022 at 22:31, Hans Henrik Bergan 
>> wrote:
>>
>>> i have a 40-core 128GB RAM server with 1 (and only 1) static ipv4
>>> address that I intend to keep around until at least 27 november 2025 (but
>>> unsure after that),
>>> it has more RAM/CPU than i need, and i could set up a virtual machine on
>>> it and give VNC access to the VM in the form of
>>> > ssh -L :localhost:3389 user@ip
>>> then point a RDP/VNC client to localhost:
>>> i can dedicate individual TCP ports to it, but not any of 22, 80, 443,
>>> 5900,  5901, 8083, , 587, 2525
>>> (after which i can recommend Teamviewer for a more comfortable access)
>>>
>>> but the server has several caveats:
>>> - it's un-raided, rolling just a single 1TB SSD, if that SSD was to die,
>>> everything on it would be lost, and it would probably take days to replace
>>> the drive.
>>> - it's located in a somewhat unstable environment, occasional power
>>> outage, it was out on 30 june, 23 june, 27 january, and in 2021 was down on
>>> 30 august. (it boots up and recovers automatically, but it has a reboot
>>> time of roughly 300 seconds until ssh responds again)
>>> - I can not offer a dedicated IP (but can offer some dedicated ports)
>>> - May be 

Re: [PHP-DEV] Windows PECL build machine died

2022-07-22 Thread Hans Henrik Bergan
10 days of radio silence? What's going on? anyway benchmarks (countsey of
bench.sh ) of the server/bandwidth

 A Bench.sh Script By Teddysun ---
 Version: v2022-06-01
 Usage  : wget -qO- bench.sh | bash
--
 CPU Model  : Intel(R) Xeon(R) CPU E7- 4870  @ 2.40GHz
 CPU Cores  : 40 @ 2524.597 MHz
 CPU Cache  : 30720 KB
 AES-NI : Enabled
 VM-x/AMD-V : Enabled
 Total Disk : 393.6 GB (48.7 GB Used)
 Total Mem  : 125.9 GB (12.0 GB Used)
 Total Swap : 8.0 GB (0 Used)
 System uptime  : 10 days, 2 hour 11 min
 Load average   : 40.18, 40.10, 40.13
 OS : Ubuntu 20.04.4 LTS
 Arch   : x86_64 (64 Bit)
 Kernel : 5.4.0-122-generic
 TCP CC : cubic
 Virtualization : Dedicated
 Organization   : AS31798 DataCity
 Location   : Kitchener / CA
 Region : Ontario
--
 I/O Speed(1st run) : 812 MB/s
 I/O Speed(2nd run) : 841 MB/s
 I/O Speed(3rd run) : 821 MB/s
 I/O Speed(average) : 824.7 MB/s
--
 Node NameUpload Speed  Download Speed  Latency
 Speedtest.net941.15 Mbps   829.87 Mbps 3.09 ms
 Los Angeles, US  937.01 Mbps   903.15 Mbps 64.21 ms
 Dallas, US   941.23 Mbps   898.69 Mbps 36.36 ms
 Montreal, CA 888.80 Mbps   916.91 Mbps 11.09 ms
 Paris, FR886.36 Mbps   820.77 Mbps 90.50 ms
 Amsterdam, NL854.88 Mbps   770.73 Mbps 98.16 ms
 Shanghai, CN 426.16 Mbps   833.23 Mbps 216.21 ms
 Nanjing, CN  439.53 Mbps   542.91 Mbps 198.60 ms
 Seoul, KR465.37 Mbps   367.20 Mbps 216.88 ms
 Singapore, SG417.93 Mbps   132.76 Mbps 212.71 ms
 Tokyo, JP668.62 Mbps   676.35 Mbps 134.48 ms
--
 Finished in: 5 min 35 sec
 Timestamp  : 2022-07-22 21:35:37 UTC
--

- it incorrectly says 393GB because of partitioning, it's actually 1TB

- I've intentionally disabled Hyperthreading because... in my
opinion/experience, hyperthreading implementations in older Intel CPUs
often did more harm than good, making the cpus run hotter and clock lower,
this is a (high-end) 2011 model. (I have the opposite experience with AMD
SMT fwiw)



On Thu, 14 Jul 2022 at 01:18, Hans Henrik Bergan 
wrote:

> Fwiw Chris Haas / vendiadvertising.com has reached out, they're willing
> to sponsor raid(1) if my proposal is accepted.
> Haas is reading this mailing list, but does not wish to participate/post
> directly at present.
> (I have no prior relation, never heard of them before today)
>
> On Tue, 12 Jul 2022 at 22:31, Hans Henrik Bergan 
> wrote:
>
>> i have a 40-core 128GB RAM server with 1 (and only 1) static ipv4 address
>> that I intend to keep around until at least 27 november 2025 (but unsure
>> after that),
>> it has more RAM/CPU than i need, and i could set up a virtual machine on
>> it and give VNC access to the VM in the form of
>> > ssh -L :localhost:3389 user@ip
>> then point a RDP/VNC client to localhost:
>> i can dedicate individual TCP ports to it, but not any of 22, 80, 443,
>> 5900,  5901, 8083, , 587, 2525
>> (after which i can recommend Teamviewer for a more comfortable access)
>>
>> but the server has several caveats:
>> - it's un-raided, rolling just a single 1TB SSD, if that SSD was to die,
>> everything on it would be lost, and it would probably take days to replace
>> the drive.
>> - it's located in a somewhat unstable environment, occasional power
>> outage, it was out on 30 june, 23 june, 27 january, and in 2021 was down on
>> 30 august. (it boots up and recovers automatically, but it has a reboot
>> time of roughly 300 seconds until ssh responds again)
>> - I can not offer a dedicated IP (but can offer some dedicated ports)
>> - May be decommissioned after 27-11-2025
>>
>> If that sounds like a good idea, I'll want a ssh public key.
>>
>>
>> On Tue, 12 Jul 2022 at 15:38, Christoph M. Becker 
>> wrote:
>>
>>> On 11.07.2022 at 21:04, Hans Henrik Bergan wrote:
>>>
>>> > Any of you windows.php.net guys familiar with SSH? Can one be created?
>>>
>>> That would be possible (needed to be set-up by Alex Schoenmaker), but
>>> while that could solve the upload issue, it wouldn't solve the other
>>> issue I've mentioned, namely that we need to avoid dynamically linking
>>> against incompatible versions of dependencies.  And there is yet another
>>> issue, namely security.  I think these issues can only be solved by some
>>> central place where the packages are build.
>>>
>>> > On Mon, 11 Jul 2022 at 

Re: [PHP-DEV] Windows PECL build machine died

2022-07-13 Thread Hans Henrik Bergan
Fwiw Chris Haas / vendiadvertising.com has reached out, they're willing to
sponsor raid(1) if my proposal is accepted.
Haas is reading this mailing list, but does not wish to participate/post
directly at present.
(I have no prior relation, never heard of them before today)

On Tue, 12 Jul 2022 at 22:31, Hans Henrik Bergan 
wrote:

> i have a 40-core 128GB RAM server with 1 (and only 1) static ipv4 address
> that I intend to keep around until at least 27 november 2025 (but unsure
> after that),
> it has more RAM/CPU than i need, and i could set up a virtual machine on
> it and give VNC access to the VM in the form of
> > ssh -L :localhost:3389 user@ip
> then point a RDP/VNC client to localhost:
> i can dedicate individual TCP ports to it, but not any of 22, 80, 443,
> 5900,  5901, 8083, , 587, 2525
> (after which i can recommend Teamviewer for a more comfortable access)
>
> but the server has several caveats:
> - it's un-raided, rolling just a single 1TB SSD, if that SSD was to die,
> everything on it would be lost, and it would probably take days to replace
> the drive.
> - it's located in a somewhat unstable environment, occasional power
> outage, it was out on 30 june, 23 june, 27 january, and in 2021 was down on
> 30 august. (it boots up and recovers automatically, but it has a reboot
> time of roughly 300 seconds until ssh responds again)
> - I can not offer a dedicated IP (but can offer some dedicated ports)
> - May be decommissioned after 27-11-2025
>
> If that sounds like a good idea, I'll want a ssh public key.
>
>
> On Tue, 12 Jul 2022 at 15:38, Christoph M. Becker 
> wrote:
>
>> On 11.07.2022 at 21:04, Hans Henrik Bergan wrote:
>>
>> > Any of you windows.php.net guys familiar with SSH? Can one be created?
>>
>> That would be possible (needed to be set-up by Alex Schoenmaker), but
>> while that could solve the upload issue, it wouldn't solve the other
>> issue I've mentioned, namely that we need to avoid dynamically linking
>> against incompatible versions of dependencies.  And there is yet another
>> issue, namely security.  I think these issues can only be solved by some
>> central place where the packages are build.
>>
>> > On Mon, 11 Jul 2022 at 19:52, Christoph M. Becker 
>> wrote:
>> >
>> >> On 11.07.2022 at 18:53, Hans Henrik Bergan wrote:
>> >>
>> >>> Is there any SSH public key associated with the Windows php
>> developers?
>> >> Or
>> >>> with CMB?
>> >>
>> >> No.  At least not regarding windows.php.net.
>> >>
>> >>> On Mon, 11 Jul 2022 at 18:25, Christoph M. Becker 
>> >> wrote:
>> >>>
>>  On 11.07.2022 at 17:41, Hans Henrik Bergan wrote:
>> 
>> > Do you mean it is unlikely that Github Actions will suffice? because
>> >> that
>> > would definitely be a great solution if it was possible/feasible .
>> 
>>  No.  It is only unlikely that automated uploads to window.php.net
>> will
>>  ever be possible using GH actions.
>> 
>> > Anyway, with regards to "I don't think there are special
>> requirements
>> > regarding the hardware", can you give a rough estimate on RAM/disk
>> >> space
>> > requirements?
>> 
>>  The old machine had something like 4 or 8 GB RAM, and a 128 GB hard
>> >> disk.
>> 
>> >>>
>> >>
>> >
>>
>>


Re: [PHP-DEV] Windows PECL build machine died

2022-07-12 Thread Hans Henrik Bergan
i have a 40-core 128GB RAM server with 1 (and only 1) static ipv4 address
that I intend to keep around until at least 27 november 2025 (but unsure
after that),
it has more RAM/CPU than i need, and i could set up a virtual machine on it
and give VNC access to the VM in the form of
> ssh -L :localhost:3389 user@ip
then point a RDP/VNC client to localhost:
i can dedicate individual TCP ports to it, but not any of 22, 80, 443,
5900,  5901, 8083, , 587, 2525
(after which i can recommend Teamviewer for a more comfortable access)

but the server has several caveats:
- it's un-raided, rolling just a single 1TB SSD, if that SSD was to die,
everything on it would be lost, and it would probably take days to replace
the drive.
- it's located in a somewhat unstable environment, occasional power outage,
it was out on 30 june, 23 june, 27 january, and in 2021 was down on 30
august. (it boots up and recovers automatically, but it has a reboot time
of roughly 300 seconds until ssh responds again)
- I can not offer a dedicated IP (but can offer some dedicated ports)
- May be decommissioned after 27-11-2025

If that sounds like a good idea, I'll want a ssh public key.


On Tue, 12 Jul 2022 at 15:38, Christoph M. Becker  wrote:

> On 11.07.2022 at 21:04, Hans Henrik Bergan wrote:
>
> > Any of you windows.php.net guys familiar with SSH? Can one be created?
>
> That would be possible (needed to be set-up by Alex Schoenmaker), but
> while that could solve the upload issue, it wouldn't solve the other
> issue I've mentioned, namely that we need to avoid dynamically linking
> against incompatible versions of dependencies.  And there is yet another
> issue, namely security.  I think these issues can only be solved by some
> central place where the packages are build.
>
> > On Mon, 11 Jul 2022 at 19:52, Christoph M. Becker 
> wrote:
> >
> >> On 11.07.2022 at 18:53, Hans Henrik Bergan wrote:
> >>
> >>> Is there any SSH public key associated with the Windows php developers?
> >> Or
> >>> with CMB?
> >>
> >> No.  At least not regarding windows.php.net.
> >>
> >>> On Mon, 11 Jul 2022 at 18:25, Christoph M. Becker 
> >> wrote:
> >>>
>  On 11.07.2022 at 17:41, Hans Henrik Bergan wrote:
> 
> > Do you mean it is unlikely that Github Actions will suffice? because
> >> that
> > would definitely be a great solution if it was possible/feasible .
> 
>  No.  It is only unlikely that automated uploads to window.php.net
> will
>  ever be possible using GH actions.
> 
> > Anyway, with regards to "I don't think there are special requirements
> > regarding the hardware", can you give a rough estimate on RAM/disk
> >> space
> > requirements?
> 
>  The old machine had something like 4 or 8 GB RAM, and a 128 GB hard
> >> disk.
> 
> >>>
> >>
> >
>
>


Re: [PHP-DEV] Windows PECL build machine died

2022-07-12 Thread Christoph M. Becker
On 11.07.2022 at 21:04, Hans Henrik Bergan wrote:

> Any of you windows.php.net guys familiar with SSH? Can one be created?

That would be possible (needed to be set-up by Alex Schoenmaker), but
while that could solve the upload issue, it wouldn't solve the other
issue I've mentioned, namely that we need to avoid dynamically linking
against incompatible versions of dependencies.  And there is yet another
issue, namely security.  I think these issues can only be solved by some
central place where the packages are build.

> On Mon, 11 Jul 2022 at 19:52, Christoph M. Becker  wrote:
>
>> On 11.07.2022 at 18:53, Hans Henrik Bergan wrote:
>>
>>> Is there any SSH public key associated with the Windows php developers?
>> Or
>>> with CMB?
>>
>> No.  At least not regarding windows.php.net.
>>
>>> On Mon, 11 Jul 2022 at 18:25, Christoph M. Becker 
>> wrote:
>>>
 On 11.07.2022 at 17:41, Hans Henrik Bergan wrote:

> Do you mean it is unlikely that Github Actions will suffice? because
>> that
> would definitely be a great solution if it was possible/feasible .

 No.  It is only unlikely that automated uploads to window.php.net will
 ever be possible using GH actions.

> Anyway, with regards to "I don't think there are special requirements
> regarding the hardware", can you give a rough estimate on RAM/disk
>> space
> requirements?

 The old machine had something like 4 or 8 GB RAM, and a 128 GB hard
>> disk.

>>>
>>
>

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php



Re: [PHP-DEV] Windows PECL build machine died

2022-07-11 Thread Hans Henrik Bergan
Any of you windows.php.net guys familiar with SSH? Can one be created?

On Mon, 11 Jul 2022 at 19:52, Christoph M. Becker  wrote:

> On 11.07.2022 at 18:53, Hans Henrik Bergan wrote:
>
> > Is there any SSH public key associated with the Windows php developers?
> Or
> > with CMB?
>
> No.  At least not regarding windows.php.net.
>
> > On Mon, 11 Jul 2022 at 18:25, Christoph M. Becker 
> wrote:
> >
> >> On 11.07.2022 at 17:41, Hans Henrik Bergan wrote:
> >>
> >>> Do you mean it is unlikely that Github Actions will suffice? because
> that
> >>> would definitely be a great solution if it was possible/feasible .
> >>
> >> No.  It is only unlikely that automated uploads to window.php.net will
> >> ever be possible using GH actions.
> >>
> >>> Anyway, with regards to "I don't think there are special requirements
> >>> regarding the hardware", can you give a rough estimate on RAM/disk
> space
> >>> requirements?
> >>
> >> The old machine had something like 4 or 8 GB RAM, and a 128 GB hard
> disk.
> >>
> >
>


Re: [PHP-DEV] Windows PECL build machine died

2022-07-11 Thread Christoph M. Becker
On 11.07.2022 at 18:53, Hans Henrik Bergan wrote:

> Is there any SSH public key associated with the Windows php developers? Or
> with CMB?

No.  At least not regarding windows.php.net.

> On Mon, 11 Jul 2022 at 18:25, Christoph M. Becker  wrote:
>
>> On 11.07.2022 at 17:41, Hans Henrik Bergan wrote:
>>
>>> Do you mean it is unlikely that Github Actions will suffice? because that
>>> would definitely be a great solution if it was possible/feasible .
>>
>> No.  It is only unlikely that automated uploads to window.php.net will
>> ever be possible using GH actions.
>>
>>> Anyway, with regards to "I don't think there are special requirements
>>> regarding the hardware", can you give a rough estimate on RAM/disk space
>>> requirements?
>>
>> The old machine had something like 4 or 8 GB RAM, and a 128 GB hard disk.
>>
>

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php



Re: [PHP-DEV] Windows PECL build machine died

2022-07-11 Thread Hans Henrik Bergan
Is there any SSH public key associated with the Windows php developers? Or
with CMB?

On Mon, 11 Jul 2022 at 18:25, Christoph M. Becker  wrote:

> On 11.07.2022 at 17:41, Hans Henrik Bergan wrote:
>
> > Do you mean it is unlikely that Github Actions will suffice? because that
> > would definitely be a great solution if it was possible/feasible .
>
> No.  It is only unlikely that automated uploads to window.php.net will
> ever be possible using GH actions.
>
> > Anyway, with regards to "I don't think there are special requirements
> > regarding the hardware", can you give a rough estimate on RAM/disk space
> > requirements?
>
> The old machine had something like 4 or 8 GB RAM, and a 128 GB hard disk.
>


Re: [PHP-DEV] Windows PECL build machine died

2022-07-11 Thread Christoph M. Becker
On 11.07.2022 at 17:41, Hans Henrik Bergan wrote:

> Do you mean it is unlikely that Github Actions will suffice? because that
> would definitely be a great solution if it was possible/feasible .

No.  It is only unlikely that automated uploads to window.php.net will
ever be possible using GH actions.

> Anyway, with regards to "I don't think there are special requirements
> regarding the hardware", can you give a rough estimate on RAM/disk space
> requirements?

The old machine had something like 4 or 8 GB RAM, and a 128 GB hard disk.

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php



Re: [PHP-DEV] Windows PECL build machine died

2022-07-11 Thread Hans Henrik Bergan
Do you mean it is unlikely that Github Actions will suffice? because that
would definitely be a great solution if it was possible/feasible .

Anyway, with regards to "I don't think there are special requirements
regarding the hardware", can you give a rough estimate on RAM/disk space
requirements?


Re: [PHP-DEV] Windows PECL build machine died

2022-07-11 Thread Christoph M. Becker
On 11.07.2022 at 09:27, James Titcumb wrote:

> On Fri, 8 Apr 2022 at 15:29, Calvin Buckley  wrote:
>
>> If I could set up a workflow that when I tag a release, it pushes a full
>> matrix to PECL, that would be great.
>
> Any info on whether this is possible, or may be possible in the future? I
> too have set up a pipeline to build all supported PHP versions for
> scoutapm, on nts/ts, x86/x64 (big thanks to cmb!). Would be nice if that
> build matrix could also upload the DLLs built in GitHub Actions to PECL,
> but I have no idea what the steps to do that (starting from a built DLL)
> would be.

This is unlikely to be possible even in the future.  For once, the FTP
server is configured to only accept uploads from an IP whitelist.  But
maybe more importantly, we need to avoid DLL hell and ABI breaks for
users, so especially if there are libraries involved, we need to make
sure that these are the same version, or at least compatible, between
different extensions.

I'm hoping that  can serve as a base
for doing the official Windows builds of PECL extensions, but there is
still a lot of work to do (most notably regarding the PECL dependency
libraries[1], which are not yet properly versioned[2]).

[1] 
[2] 

--
Christoph M. Becker

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php



Re: [PHP-DEV] Windows PECL build machine died

2022-07-11 Thread James Titcumb
Hi folks

On Fri, 8 Apr 2022 at 15:29, Calvin Buckley  wrote:

> If I could set up a workflow that when I tag a release, it pushes a full
> matrix to PECL, that would be great.
>

Any info on whether this is possible, or may be possible in the future? I
too have set up a pipeline to build all supported PHP versions for
scoutapm, on nts/ts, x86/x64 (big thanks to cmb!). Would be nice if that
build matrix could also upload the DLLs built in GitHub Actions to PECL,
but I have no idea what the steps to do that (starting from a built DLL)
would be.

Thanks
James


Re: [PHP-DEV] Windows PECL build machine died

2022-04-08 Thread Calvin Buckley
This might be interesting. I've set up Actions builds for extensions,
and the Windows part was pretty easy (thanks to Christoph's action for
setting up a PHP build environment on Windows). If I could set up a
workflow that when I tag a release, it pushes a full matrix to PECL,
that would be great.

On Fri, 2022-04-08 at 17:25 +0530, Ayesh Karunaratne wrote:
> With php-src's recently starting to Github Actions, would it be
> possible for PECL builds to use Github Actions with Windows. It
> supports Windows server 2016, 2019, and even 2022 (IIRC).

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php



Re: [PHP-DEV] Windows PECL build machine died

2022-04-08 Thread Ayesh Karunaratne
With php-src's recently starting to Github Actions, would it be
possible for PECL builds to use Github Actions with Windows. It
supports Windows server 2016, 2019, and even 2022 (IIRC).

On Fri, Apr 8, 2022 at 5:17 PM Christoph M. Becker  wrote:
>
> Hi all,
>
> bad news: the Windows PECL build machine died!  Is there anybody
> interested in sponsoring a successor?  That (virtual) machine would need
> to run 24/7, and to be configured to run php/web-rmtools, basically
> listening for new PECL releases, and to build them as soon as possible.
> It should run on Windows 10 Professional, or on some Windows Server 2019
> (or maybe Windows 11/Windows Server 2022); I don't think there are
> special requirements regarding the hardware.
>
> Anyhow, many thanks to Alex Schoenmaker who sponsored the old PECL build
> machine for many years!
>
> --
> Christoph M. Becker
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php



[PHP-DEV] Windows PECL build machine died

2022-04-08 Thread Christoph M. Becker
Hi all,

bad news: the Windows PECL build machine died!  Is there anybody
interested in sponsoring a successor?  That (virtual) machine would need
to run 24/7, and to be configured to run php/web-rmtools, basically
listening for new PECL releases, and to build them as soon as possible.
It should run on Windows 10 Professional, or on some Windows Server 2019
(or maybe Windows 11/Windows Server 2022); I don't think there are
special requirements regarding the hardware.

Anyhow, many thanks to Alex Schoenmaker who sponsored the old PECL build
machine for many years!

--
Christoph M. Becker

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php