Re: PEAR Box Updates

From: Date: Tue, 04 Jun 2024 12:11:30 +0000
Subject: Re: PEAR Box Updates
References: 1 2 3 4 5 6 7 8 9  Groups: php.pear.core 
Request: Send a blank email to pear-core+get-10002@lists.php.net to get a copy of this message
On 4 June 2024 12:57:29 BST, Chuck Burgess <demon.gene@gmail.com> wrote: >Thanks for checking things out, Derrick. I'll see about coming up with >alternative installation instructions for users still relying on the PEAR >site as a download channel. Once I get that figured out, I'll look at >announcing a retirement of the website. It's going to be fairly easy to make a static site out of it. But there are still some people making releases. There were a handful this year. The static site we can probably host on downloads.php.net - we're moving the windows downloads there too. cheers Derick >On Tue, Jun 4, 2024, 04:57 Derick Rethans <derick@php.net> wrote: > >> Hi, >> >> I've just had a poke around, and this machine is running a very outdated >> Debian, and also still runs PHP 5.6. I can update the OS, but that won't >> have PHP 5.6 any more. Somebody who knows the code well will have to do >> that. >> >> The database tables area also still latin1, and not utf-8. That is going >> be causing a major issue if we upgrade MariaDB (version 10 right now) >> too I suspect — it did for the PECL machine. >> >> If there is nobody that is willing to take care of that from the PEAR >> community, I suggest we perhaps should phase out the PEAR project. It is >> not responsible to have such an old machine running. >> >> The current PECL installer is still the pear installer, and bundled >> through PHP, but we are working on a new extensions installer based on >> composer tech, once the new PECL installer PIE is ready, the PHP project >> also wouldn't depend on PEAR any more. >> >> cheers, >> Derick >> >> On Sun, 2 Jun 2024, Chuck Burgess wrote: >> >> > Hey Derick, >> > Since the guys never responded, I went ahead and created your shell >> account >> > using basic instructions, assuming nothing special was needed. I also >> > added you to all the admin groups that I'm already in (e.g. *sudo*). >> > Initial password is XXXXXX... let me know if it works for you. >> > CRB >> > *about.me/ashnazg <http://about.me/ashnazg>* >> > >> > >> > On Sun, Mar 10, 2024 at 11:16 AM Chuck Burgess <demon.gene@gmail.com> >> wrote: >> > >> > > Rasmus or Martin, >> > > >> > > Can one of you create a shell account for Derick on the PEAR box? >> > > >> > > CRB >> > > *about.me/ashnazg >> > > <http://about.me/ashnazg>* >> > > >> > > >> > > On Mon, Jan 22, 2024 at 8:04 AM Chuck Burgess <demon.gene@gmail.com> >> > > wrote: >> > > >> > >> Yes, jump box is in place. I'll defer to the others on creating the >> > >> shell account. >> > >> CRB >> > >> >> > >> On Mon, Jan 22, 2024, 07:30 Derick Rethans <derick@php.net> wrote: >> > >> >> > >>> Hi, >> > >>> >> > >>> I don't have ssh access to the machine. The wiki says that only mj, >> > >>> rasmus, and cweiske have that. I've cced them in case they can give >> me >> > >>> access (unless you can too). >> > >>> >> > >>> Is the jump server setup for this machine too? (is, no access without >> > >>> going through our bastion? >> > >>> >> > >>> cheers >> > >>> Derick >> > >>> >> > >>> >> > >>> On 20 January 2024 16:55:35 GMT, Chuck Burgess <demon.gene@gmail.com >> > >> > >>> wrote: >> > >>> >Yes please, Derick, if you could do those upgrades, that would be >> great >> > >>> :) >> > >>> >I don't actually know which *service *hosts the box, just that >> > >>> >as * >> > >>> pear.php.net >> > >>> ><http://pear.php.net>*, >> > >>> >it's one of the *php.net <http://php.net> >> > >>> *boxes, >> > >>> >so my *general-guess* answer would be "*you guys*" ;) >> > >>> >CRB >> > >>> >*about.me/ashnazg <%â\ §@‰v >> > >>> >­ŠüShttp://about.me/ashnazg>* >> > >>> > >> > >>> > >> > >>> >On Mon, Jan 15, 2024 at 1:13 PM Derick Rethans >> > >>> ><derick@php.net> >> wrote: >> > >>> > >> > >>> >> On 15 January 2024 18:48:49 GMT, Chuck Burgess < >> demon.gene@gmail.com> >> > >>> >> wrote: >> > >>> >> >Hey folks, >> > >>> >> > >> > >>> >> >I was troubleshooting an issue with *Apache *on the *PEAR* >> > >>> >> >box, >> when >> > >>> I >> > >>> >> >realized that I don't actually know who is >> > >>> >> >responsible/allowed to >> > >>> pull in >> > >>> >> >package updates from *apt* for that box. As* root,* am I >> > >>> >> >clear >> to be >> > >>> >> doing >> > >>> >> >that myself? Or should I defer to the security team? >> > >>> >> >I'm >> > >>> definitely a >> > >>> >> bit >> > >>> >> >leery of performing a *box restart* myself, since I'd >> > >>> >> >have no >> clue >> > >>> who to >> > >>> >> >contact (aside from this list) if the box didn't come >> > >>> >> >back up >> clean. >> > >>> >> > >> > >>> >> >CRB >> > >>> >> >*about.me/ashnazg >> > >>> >> ><http://about.me/ashnazg>* >> > >>> >> >> > >>> >> Who hosts the box? >> > >>> >> >> > >>> >> I wouldn't be too worried about upgrading the machine. If >> > >>> >> you'd >> prefer >> > >>> >> someone else to do that, I can, as I've been doing it for >> > >>> >> all non >> pear >> > >>> >> machines. We'd likely need yobuigrade to bookworm too. >> > >>> >> >> > >>> >> cheers >> > >>> >> Derick >> > >>> >> >> > >>> >> > >>> >> > >> >> -- >> https://derickrethans.nl | >> https://xdebug.org | https://dram.io >> >> Author of Xdebug. Like it? Consider supporting me: >> https://xdebug.org/support >> >> mastodon: @derickr@phpc.social @xdebug@phpc.social

« previous php.pear.core (#10002) next »