-
Notifications
You must be signed in to change notification settings - Fork 603
Fix typo in LIBMIT_KRB5 variable naming #2335
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Looking at the resulting configure script I believe this was a typo
rousskov
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@timp87, thank you for fixing this! We fixed (and discovered) the same bug during recent #2320 work, but that PR has not been merged yet, and it is probably best to merge your smaller/focused PR first.
When you were porting Squid v7 to FreeBSD, how did this typo manifest itself? In other words, what were the symptoms of this bug that draw your attention to it?
I tried to identify the commit that broke this, but I could not do it quickly with enough certainty. AFAICT, the first explicit mention of LIBMIT_KRB5 happened in 2024 commit d99af84, but it is possible that a different commit is responsible.
I adjusted PR description (i.e. the future official commit message), primarily to avoid duplicating PR title (adjusted earlier by Amos).
|
Similar to #2337 (comment) |
Discovered while porting Squid v7 to FreeBSD.
Discovered while porting Squid v7 to FreeBSD.
Backport is already in progress at #2339. Backporting process/automation is undergoing changes right now, triggering some noise and delays, but all of that is unrelated to your work and this specific PR. The ball is on our side. |
|
Ok, just didn't see a message from the bot about backport queueing like in other PRs |
Discovered while porting Squid v7 to FreeBSD.
Discovered while porting Squid v7 to FreeBSD.