Skip to content

Conversation

@fraggerfox
Copy link
Contributor

@fraggerfox fraggerfox commented Nov 24, 2025

  • Upgrade OpenBSD to 7.8.
    • But relax warnings for the CI to not fail (we still run the test suite against it).
  • Bump FreeBSD version to the latest supported 15.0.

Release notes can be found here:

@fraggerfox fraggerfox force-pushed the ci-upgrade-openbsd-78 branch from 64ec8f1 to 37b344c Compare November 27, 2025 21:24
@fraggerfox fraggerfox force-pushed the ci-upgrade-openbsd-78 branch from 37b344c to b13eb9e Compare December 6, 2025 18:24
@fraggerfox fraggerfox changed the title chore: Upgrade OpenBSD to 7.8 in CI. chore: Upgrade FreeBSD / OpenBSD in CI. Dec 7, 2025
@fraggerfox fraggerfox force-pushed the ci-upgrade-openbsd-78 branch 4 times, most recently from 20578fe to 847ea97 Compare December 10, 2025 23:14
Until we can add support for OpenBSD in rustup.
@fraggerfox fraggerfox force-pushed the ci-upgrade-openbsd-78 branch from 847ea97 to 14c49c3 Compare December 10, 2025 23:22
set -e
export CARGO_TERM_COLOR="always"
export RUSTFLAGS="--deny warnings"
# Do not treat warnings as failure, since OpenBSD lags behind "rustup" versions.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cafkafk: I am aware that the following change is not the most ideal, but it should still run the tests in the CI against OpenBSD.

With 7.7 reaching EoL in about 4 months (at the time of writing), the CI in due course of time may fail to fetch packages for 7.7 via pkg_add

Looking at the issues from

It looks like there is a bit of effort involved in making rustup pickup and support OpenBSD too since it is considered a tier 3 platform.

For now this work around is the best solution I can think of, until I can figure out a way to get it to play along like the other two BSDs.

Let me know, what you think and if this is an acceptable compromise.

@fraggerfox fraggerfox marked this pull request as ready for review December 10, 2025 23:43
Copy link
Contributor

@ariasuni ariasuni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me

Copy link
Member

@gierens gierens left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me, as well. Disabling warnings and clippy only on FreeBSD/OpenBSD shouldn't be a problem. Anything relevant they might flag, should also be caught by the CI jobs for the other platforms.

@fraggerfox
Copy link
Contributor Author

This looks good to me, as well. Disabling warnings and clippy only on FreeBSD/OpenBSD shouldn't be a problem. Anything relevant they might flag, should also be caught by the CI jobs for the other platforms.

Warnings / clippy are disabled only for OpenBSD, since FreeBSD has proper rustup support.

@gierens
Copy link
Member

gierens commented Dec 30, 2025

Warnings / clippy are disabled only for OpenBSD, since FreeBSD has proper rustup support.

Thanks for the hint, yeah, then it seems even less of a problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants