Skip to content

Conversation

@fraggerfox
Copy link
Contributor

@fraggerfox fraggerfox commented Nov 23, 2025

  • Bump FreeBSD version to the latest supported 14.3
  • Bump DragonFlyBSD version to the latest supported 6.4.2
  • Bump OpenBSD version to the latest supported 7.8

Release notes can be found here:

@fraggerfox fraggerfox force-pushed the ci-bump-bsd-version branch 3 times, most recently from 6666d82 to efffb0d Compare November 23, 2025 13:18
proc->time = 100 * (kproc->p_rtime_sec + ((kproc->p_rtime_usec + 500000) / 1000000));
proc->priority = kproc->p_priority - PZERO;
proc->processor = kproc->p_cpuid;
proc->processor = (int) kproc->p_cpuid;
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Based on this https://github.com/openbsd/src/blob/master/sys/sys/sysctl.h , I think this conversion should work?

Copy link
Member

Choose a reason for hiding this comment

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

Looks fine for now, I don't know of any machines with MAXINT CPUs today or in the near future.

Copy link
Member

Choose a reason for hiding this comment

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

Wondering when loongarch will reach MAXLONG CPUs … /jk

@fraggerfox fraggerfox marked this pull request as ready for review November 23, 2025 14:03
@BenBE
Copy link
Member

BenBE commented Nov 24, 2025

Reorder the commits to first fix the issues and then bump the versions:

  • Merge the int size fixes (commits 3+4)
  • Do the OpenBSD fixes (may also be squashed into the first step)
  • Bump the versions

Apart from this LGTM.

@BenBE BenBE merged commit 27a71f3 into htop-dev:main Nov 27, 2025
20 checks passed
@fraggerfox fraggerfox deleted the ci-bump-bsd-version branch November 27, 2025 23:38
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.

4 participants