Post B5FWAU8HwJTLeykxbE by joel@tumfatig.net
 (DIR) More posts by joel@tumfatig.net
 (DIR) Post #B5FTpRV2KnBZVJEe12 by joel@tumfatig.net
       0 likes, 1 repeats
       
       Thanks to @libreleah 🫶, my stupid self is not using the corrupted fox anymore on #OpenBSD. The "stable-7.8" version of #Librewolf is a bit old but seem to work as expected.https://mas.to/@libreleah/116345551259228600
       
 (DIR) Post #B5FTqLNsYajapKJidM by libreleah@mas.to
       0 likes, 0 repeats
       
       @joel You, comrade, have made my day. Thank you!I'm currently build-testing the latest LibreWolf on OpenBSD -CURRENT. Hopefully I'll have that working soon (build works perfectly on 7.8 with LibreWolf 143, as in your post, but I had problems the other day with 149 on -CURRENT / 7.9-snapshot).Hopefully I can get everything going and send a patch to ports team ready for 7.9 proper.
       
 (DIR) Post #B5FU0tlZa0HaMCQsMa by libreleah@mas.to
       0 likes, 0 repeats
       
       @joel I think the issue the other day is I had old toolchains / libs polluting the build, because I'd done full dependencies and everything on 7.8, and *then* updated to CURREENT.I re-did my OpenBSD install yesterday, this time on a proper RAID1c setup too, and only installed base, then immediately upgraded to -CURRENT.And I did not install anything in pkg_add. All I did was set up ports repo, and I'm running "make package".I think my port is OK on current. I just needed to purge it clean.
       
 (DIR) Post #B5FUBUSpzcfr4LigsK by libreleah@mas.to
       0 likes, 0 repeats
       
       @joel the reason I used librewolf 143 on 7.8 is because firefox 143 is used on obsd 7.8. my port tracks www/mozilla-firefox. i'm doing it this way to keep patches and such in sync. to avoid duplication of labour.
       
 (DIR) Post #B5FVVfyZ0CPaWAkTBo by joel@tumfatig.net
       0 likes, 0 repeats
       
       @libreleah oh, ok. I wondered if this was due to some dependencies. I used to use ESR so I’m not really bothered with old versions :DI don’t do -snapshot in general so I would wait for 7.9 to come out before upgrading.
       
 (DIR) Post #B5FVVgC2C7BfBx3EBc by libreleah@mas.to
       0 likes, 0 repeats
       
       @joel that's fine, but port maintainers have to use -CURRENT. openbsd port maintenance happens in CURRENT, and they freeze it in a new branch per release.i started with 7.8 just to bootstrap my porting work. i probably should have just started straight from current.anyway, congrats for getting that to build. that build is brutal. it takes about 5 hours on my computer!
       
 (DIR) Post #B5FWAU8HwJTLeykxbE by joel@tumfatig.net
       0 likes, 0 repeats
       
       @libreleah yeah, got used to this. Only security patched get backported. I’m ok with that. The only time I used -snapshots was when Xfce 4.20 was ported. I couldn’t wait for the new Thunar features at that time 😅I have not mesured but it probably took like 2-3 hours here (AMD Ryzen with 8 cores @ 3 GHz). Not sure I have another spare laptop that has this power to test a -snapshot. 🤔
       
 (DIR) Post #B5FWAUMp4H6AO3YZFo by libreleah@mas.to
       0 likes, 0 repeats
       
       @joel i feel like maybe there should be a separate repository for users who want to install specific packages. a backport repo. i could maybe maintain one, but eh. too much work.openbsd does releases every 6 months so it's not too bad. not like debian for example, where you're stuck on the same browser version for two years.i actually did try to port 149 to 7.8, but 7.8 had a slightly too old version of rustc. on debian-stable i build it with rustup. is rustup available for openbsd?
       
 (DIR) Post #B5FXBctQxCoZ4cusU4 by libreleah@mas.to
       0 likes, 0 repeats
       
       @georgsassen @joel oh really? i don't have a 7.8 machine to test with at the moment, but i can try later.i just assumed they froze whatever what was in current at each release, and packages stayed static until the next release. notwithstanding bug fixes.
       
 (DIR) Post #B5FXMlNljP48aWPqYy by libreleah@mas.to
       0 likes, 0 repeats
       
       @georgsassen @joel since i'm only using current, i don't bother with cvs. i use the github mirror of ports, which matches cvs at whatever the current revision is. easier. i hate cvs.i will only use cvs when sending a patch. git can outpuut patch files in cvs format, so, happy days.but the github mirror just has a master branch matching the main branch from cvs.
       
 (DIR) Post #B5FcD6K3WNMsPKtJWC by joel@tumfatig.net
       0 likes, 0 repeats
       
       @libreleah no idea 🤷‍♂️
       
 (DIR) Post #B5FcD6aiWQhBF0gcUK by joel@tumfatig.net
       0 likes, 0 repeats
       
       @libreleah so, I did a few updates and tried compiling your master branch on the 7.8 port branch. Seems like rust version is ok but what is not is icu4c:checking for rustc... /usr/local/bin/rustcchecking for cargo... /usr/local/bin/cargochecking rustc version... 1.90.0checking cargo version... 1.90.0checking for rust host triplet... x86_64-unknown-openbsdchecking for rust target triplet... x86_64-unknown-openbsdchecking for rustdoc... /usr/local/bin/rustdocchecking for cbindgen... /usr/local/bin/cbindgenchecking for rustfmt... not foundchecking for clang for bindgen... /usr/ports/pobj/librewolf-149.0/bin/c++checking for libclang for bindgen... /usr/local/llvm21/lib/libclang.so.0.0checking that libclang is new enough... yeschecking bindgen cflags... ['-x', 'c++', '-fno-sized-deallocation', '-fno-aligned-new', '-DTRACING=1', '-DIMPL_LIBXUL', '-DMOZILLA_INTERNAL_API', '-DRUST_BINDGEN', '-std=gnu++20']checking for libffi > 3.0.9... yeschecking MOZ_FFI_CFLAGS... -I/usr/local/includechecking MOZ_FFI_LIBS... -L/usr/local/lib -lffichecking for icu-uc icu-i18n >= 78.1... noERROR: Package dependency requirement 'icu-i18n >= 78.1' could not be satisfied.ERROR: Package 'icu-i18n' has version '77.1', required version is '>= 78.1'*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:3030 'do-configure': @cd /usr/ports/pobj/librewolf-149.0/build-amd64 && /usr/bin/...)*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:3050 '/usr/ports/pobj/librewolf-149.0/build-amd64/.configure_done': @cd /usr/port...)*** Error 2 in /usr/ports/www/librewolf (/usr/ports/infrastructure/mk/bsd.port.mk:2712 'configure': @lock=librewolf-149.0p1;  export _LOCKS_...)This could probably be solved by backporting icu4c 78 to this stable port. But... been there, done that... this impacts every other applications that rely on it... and there are quite a few here.# pkg_info -R icu4cInformation for inst:icu4c-77.1v0Required by:boost-1.87.0p0v0gspell-1.14.1harfbuzz-icu-12.1.0libical-3.0.20librewolf-143.0.3p1node-22.22.2v0orage-4.20.2qt6-qtbase-6.8.3p4qt6-qtwebengine-6.8.3p3qtbase-5.15.16pl130p0vlc-3.0.21p8vte3-0.80.4webkitgtk41-2.48.7p0So I guess trying to get Librewolf 149.0 on OpenBSD 7.8 means recompile a bunch of other software. Probably not worth the adventure when OpenBSD 7.9 should land quite soon now.
       
 (DIR) Post #B5FcD6trNG0YCNduKG by libreleah@mas.to
       0 likes, 0 repeats
       
       @joel openbsd releases every 6 months. just wait 6 months, or use CURRENT
       
 (DIR) Post #B5Fw2TsBcQqzLW4KLQ by 6d03@mathstodon.xyz
       0 likes, 0 repeats
       
       @libreleah @joel Does this work as a drop-in replacement for Firefox?