Skip to content
Snippets Groups Projects
Commit 2310df0f authored by Asterisk Development Team's avatar Asterisk Development Team
Browse files

Update for 21.1.0-rc2

parent e735ab8c
No related branches found
Tags 21.1.0-rc2
No related merge requests found
21.1.0-rc1
21.1.0-rc2
ChangeLogs/ChangeLog-21.1.0-rc1.md
\ No newline at end of file
ChangeLogs/ChangeLog-21.1.0-rc2.md
\ No newline at end of file
Change Log for Release asterisk-21.1.0-rc2
========================================
Links:
----------------------------------------
- [Full ChangeLog](https://downloads.asterisk.org/pub/telephony/asterisk/releases/ChangeLog-21.1.0-rc2.md)
- [GitHub Diff](https://github.com/asterisk/asterisk/compare/21.1.0-rc1...21.1.0-rc2)
- [Tarball](https://downloads.asterisk.org/pub/telephony/asterisk/asterisk-21.1.0-rc2.tar.gz)
- [Downloads](https://downloads.asterisk.org/pub/telephony/asterisk)
Summary:
----------------------------------------
- logger: Fix linking regression.
User Notes:
----------------------------------------
Upgrade Notes:
----------------------------------------
Closed Issues:
----------------------------------------
- #539: [bug]: Existence of logger.xml causes linking failure
Commits By Author:
----------------------------------------
- ### Naveen Albert (1):
- logger: Fix linking regression.
Detail:
----------------------------------------
- ### logger: Fix linking regression.
Author: Naveen Albert
Date: 2024-01-16
Commit 008731b0a4b96c4e6c340fff738cc12364985b64
caused a regression by resulting in logger.xml
being compiled and linked into the asterisk
binary in lieu of logger.c on certain platforms
if Asterisk was compiled in dev mode.
To fix this, we ensure the file has a unique
name without the extension. Most existing .xml
files have been named differently from any
.c files in the same directory or did not
pose this issue.
channels/pjsip/dialplan_functions.xml does not
pose this issue but is also being renamed
to adhere to this policy.
Resolves: #539
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment