Re: php-mcrypt-7.2.15?

hp.net Ian McWilliam *From:* owner-po...@openbsd.org on behalf of Scott Vanderbilt *Sent:* Tuesday, 12 February 2019 1:26 PM *To:* ports@openbsd.org *Subject:* php-mcrypt-7.2.15? Just curious if anyone knows why all t

php-mcrypt-7.2.15?

Just curious if anyone knows why all the php sub-packages for 7.2.15 were built for distribution except for php-mcrypt. I'm happy to try and builg it myself. Just wondering if it was broken or if there was some other reason why it got skipped. Thank you.

PHP 7.1+

At the risk of appearing ungrateful for all the wonderful work the ports contributors perform (which I most definitely am not), I was wondering whether it might be possible to know what the plans are for adding PHP versions 7.1 and 7.2 to the tree? If they're not in prospect, that's cool. I

Re: nano 2.5.3 (amd64) crashes

On 5/28/2016 6:05 AM, Jeremie Courreges-Anglas wrote: Scott Vanderbilt <li...@datagenic.com> writes: I just upgraded amd64 snapshots (20 April to 26 May), and refreshed my ports. nano is now dumping core on launch with following error: nano(69373) in free(): error: bogus pointer (

Re: thunderbird: Unhandleable OOM, W^X violation

This may be related to a similar issue I had with the 26 May snapshot and the JDK port. The note about fstab on sorted me out. On 5/28/2016 6:22 AM, Peter N. M. Hansteen wrote: Hi, After upgrading to the latest amd64 snapshot and packages,

nano 2.5.3 (amd64) crashes

I just upgraded amd64 snapshots (20 April to 26 May), and refreshed my ports. nano is now dumping core on launch with following error: nano(69373) in free(): error: bogus pointer (double free?) 0x440e168aca0 Abort trap (core dumped) dmesg follows. What more information can I provide that

Re: MySQL port / package in 5.6-current

On 10/20/2014 5:14 PM, Kevin wrote: What's the scoop on the MySQL port these days? It's being replaced with mariadb.

Re: MySQL port / package in 5.6-current

On 10/20/2014 5:28 PM, Kevin wrote: On Mon, Oct 20, 2014 at 5:21 PM, Scott Vanderbilt li...@datagenic.com wrote: On 10/20/2014 5:14 PM, Kevin wrote: What's the scoop on the MySQL port these days? It's being replaced with mariadb. I knew it was happening *some* day, and with the note

Replacing mysql with mariadb

Might anyone be able to furnish some advice on how to replace mysql with mariadb in -current (amd64)? Building the mariadb port in isolation is no problem whatsoever. But other ports that have mysql as a dependency are a problem, as they are (apparently) not configured to consider mariadb a

Re: JDK 1.6 Broken

On 1/1/2014 1:21 PM, Stuart Henderson wrote: Your current options are: - move to amd64. - move back to code from a month or two ago. If anyone is able to help track down the timeframe this got broken (or even pin it to a particular commit in base), that would be extremely helpful... I

Re: JDK 1.6 Broken

On 1/1/2014 6:41 AM, Marc Espie wrote: On Tue, Dec 31, 2013 at 12:14:26PM -0800, Scott Vanderbilt wrote: So I see that the jdk-1.6 port has been marked as broken, unfortunately, only after upgrading to the latest snapshot (i386). Might anyone have any idea when this will be working again

Re: JDK 1.6 Broken

On 1/1/2014 10:00 AM, Ian Darwin wrote: Given that Java 6 has been EOL'd by Oracle for almost a year (Feb 2013, as announced in Feb 2011), and it's on an operating system they don't even know about, your bug report will most likely be ignored. Sorry you wasted time there. Given the situation

Re: JDK 1.6 Broken

On 1/1/2014 1:21 PM, Stuart Henderson wrote: If anyone is able to help track down the timeframe this got broken (or even pin it to a particular commit in base), that would be extremely helpful... I was previously running a snapshot from Dec. 7 that did not exhibit the error. Sorry I can't be

JDK 1.6 Broken

So I see that the jdk-1.6 port has been marked as broken, unfortunately, only after upgrading to the latest snapshot (i386). Might anyone have any idea when this will be working again? Many thanks in advance.

re-alpine ports appears to be broken

Hello. I'm having trouble trying to build uw-imap on -current. There appears to be no maintainer for this port, thus my post here. I am running the latest available i386 snapshot: #sysctl -n kern.version OpenBSD 5.3-current (GENERIC.MP) #8: Thu Jun 20 09:51:38 MDT 2013

Re: re-alpine ports appears to be broken

Thanks very much for that. I'm not sure what I could have done differently, though. I grabbed my packages and the snapshot all within an hour or two earlier today from the same mirror. So I don't think it was a terribly unreasonable assumption on my part that they were mutually compatible. Is