[SERVER-54609] update third party notice for libunwind 1.5 Created: 18/Feb/21 Updated: 29/Oct/23 Resolved: 18/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Moody | Assignee: | Daniel Moody |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Dev Platform 2021-02-22 | ||||
| Participants: | |||||
| Linked BF Score: | 50 | ||||
| Description |
|
The third party notices still references 1.4 and was not updated at the same time the libunwind source code was. |
| Comments |
| Comment by Daniel Moody [ 18/Feb/21 ] |
|
Black Duck was incorrectly detecting some other libunwind at some other location libunwind/libunwind.
I ignored the 1.3.2 version and the libunwind/libunwind in the Black Duck tool which should fix the two related BFs. |