On Thu, Sep 30, 2021 at 09:18:23AM -0400, Greg Troxel wrote: > > Martin Husemann <mar...@duskware.de> writes: > > > On Thu, Sep 30, 2021 at 08:44:22AM -0400, Greg Troxel wrote: > >> What are people thinking about > >> > >> updating openssl to 3.0.0 in current > > > > Yes, someone(tm) should do that! Early to catch fallout quickly, but > > we'd need commitment from the pkgsrc team to make pkgsrc usefull with > > that. I don't think we need to sequence this, thing will follow naturally > > from people hitting more fallout. > > My impression is that work to make things build with 3.0.0 is in > progress, but that the fallout from a (not committed, in testing) switch > is over 5000 packages. But I expect that will rapidly get better. > > > https://us-east.manta.joyent.com/pkgsrc/public/reports/trunk/bulktest/20210928.1522/meta/report.html
Those is quite a lot of fallout. Just scouted a few, but some of the logs state that it thinks its building on x86_64-unknown-solaris2 (ghc, wayland). Is this intentional? > So if netbsd-current moves to openssl3 before pkgsrc is ready, that's > going to cause a lot of packages to break on current. So then people > who care can fix them, as usual. Can't pkgsrc do a fallback? Ie if the package is not openssl3 compatible it can fall back on an openssl 1.1 in pkgsrc until upstream is converted? Cheers, Reinoud
