Re: dependency on correct openssl?

The developers of vde2 have responded with a fix for most of the issues I reported, so now I can go test again and see if anything else is needed before we could update the port. > On Oct 5, 2019, at 14:43, Richard L. Hamilton wrote: > > No, I'd just run > port echo rdepends:vde2 > and

Re: dependency on correct openssl?

No, I'd just run port echo rdepends:vde2 and noticed virtualbox and a couple of related sub-ports in the output. Still, I gather one could also use vde2 with some builds of QEMU, for example. So it presumably still has its uses, esp. since it can apparently optionally apply degrees of network

Re: dependency on correct openssl?

Oh, gosh -- our virtualbox port is so old and out of date I wouldn't even consider using it. it should probably be removed, I guess. Do you actually have it installed? I am startled if so ! Ken On 2019-10-05, at 11:08 AM, Richard L. Hamilton wrote: > Thank you! From the tickets you

Re: dependency on correct openssl?

Thank you! From the tickets you filed, it certainly looks like you did a thorough job of investigating and reporting the issues. Hopefully they'll get to it reasonably soon, although clearly that's beyond your control. Given that virtualbox depends on it (at least if the vde2 variant is

Re: dependency on correct openssl?

On Oct 4, 2019, at 21:41, Richard L. Hamilton wrote: > I see that kdelibs4 and xmms2 are ok now; thanks to whoever did that (esp. > kdelibs4, which is probably nasty to maintain). > > The one I have left that means I can't just "port upgrade outdated" on my > system with the most packages

Re: dependency on correct openssl?

I see that kdelibs4 and xmms2 are ok now; thanks to whoever did that (esp. kdelibs4, which is probably nasty to maintain). The one I have left that means I can't just "port upgrade outdated" on my system with the most packages installed, running the current (Mojave) OS, is vde2; a look at the

Re: dependency on correct openssl?

On 8 Sep 2019, at 15:05, Ken Cunningham wrote: All your points are fair. To be honest, the PR for the openssl upgrade was in the PR queue for six months, and it was perceived that all the relevant ports that would be affected had been identified and fixed... shows you how good we are are

Re: dependency on correct openssl?

All your points are fair. To be honest, the PR for the openssl upgrade was in the PR queue for six months, and it was perceived that all the relevant ports that would be affected had been identified and fixed... shows you how good we are are guessing that! MacPorts waited about a year more

Re: dependency on correct openssl?

On 8 Sep 2019, at 2:44, Ken Cunningham wrote: Please have a bit of patience. MacPorts did a wholesale move to openssl 1.1.1 yesterday. It would be very helpful to have notice of changes this big. I made the mistake of trying an off-schedule 'upgrade outdated' yesterday and ran in to a

Re: dependency on correct openssl?

The stragglers are being tweaked as fast as we find them, eg kdelibs4 You can check the git repo, or use ports.macports.org to see how the build is going, or check the tickets to see if yours has been fixed already. Feel free to open up some tickets if

Re: dependency on correct openssl?

No big, except how can I check, short of attempting port rev-upgrade on a regular basis, when the fixes are available? I think kdelibs4 is also one that may want the older 1.0.x. > On Sep 8, 2019, at 02:44, Ken Cunningham > wrote: > > Please have a bit of patience. > > MacPorts did a

Re: dependency on correct openssl?

Please have a bit of patience. MacPorts did a wholesale move to openssl 1.1.1 yesterday. We scoped out most of the build failures prior, but there are a few that have cropped up. Some of the ones you listed have already been fixed. Best, Ken