Ticket History #9203: Windows build version higher in 1.21.x than 1.22.x

# Wed Apr 01 18:47:10 2026 Shaun Walbridge <SWalbridge@esri.com> - Ticket created

To:	"krb5-bugs@mit.edu" <krb5-bugs@mit.edu>
Date:	Wed, 1 Apr 2026 17:13:57 +0000
Subject:	1.21.3 release contains incorrect version information
From:	"Shaun Walbridge" <SWalbridge@esri.com>

Download (untitled) / with headers
text/plain 899B

Download (untitled) / with headers
text/html 3.7KiB

The builds hosted both at:

contain incorrect version information for the Windows builds. The src/windows/kerberos.ver files in this build contains:

#define KRB5_MAJOR_RELEASE 4

#define KRB5_MINOR_RELEASE 3

#define KRB5_PATCHLEVEL 0

#define KRB5_RELTAIL “beta1"

However, the more recent 1.22 releases and the development version of the codebase retain KRB5_MINOR_RELEASE 1. This means that in a Windows context, an installer will refuse to upgrade between the 1.21.3 release and 1.22 because it would downgrade the versions listed which violates the monotonic version expectations.

Locally, we are patching this so that we can continue distributing krb5, but would appreciate if this was considered as a core krb5 package issue.

Thanks for your time,

Shaun Walbridge

# Thu Apr 02 02:24:49 2026 ghudson@mit.edu (Greg Hudson) - Subject changed from '1.21.3 release contains incorrect version information' to 'Windows build version higher in 1.21.x than 1.22.x'

# Sun Apr 05 13:44:21 2026 ghudson@mit.edu (Greg Hudson) - Correspondence added

Download (untitled) / with headers
text/html 413B

I have made a note in the release engineering procedures, when increase the version numbers in windows/installer/wix/site-local.wxi and windows/kerberos.ver, also increase them on the mainline so that they don't go backwards in future release branches. I plan to prepare a KfW beta release on the 1.22 branch some time this month, so the inconsistency should resolve at that time.