Changelog for libUsageEnvironment3-2023.11.30-2.14.x86_64.rpm :

* Fri Mar 01 2024 pgajdosAATTsuse.com- Use %autosetup macro. Allows to eliminate the usage of deprecated %patchN
* Sun Jan 14 2024 Takashi Iwai - update up to 2023.11.30:
* In the implementation of the \"MPEGVideoStreamFramer\" class, gave \"TimeCode::operator==()\" the \"const\" qualifier, to make some compilers happy.
* Performed the annual update of the copyright years near the start of each file- update to 2023.11.08:
* Changed the signature to the virtual function \"getRTPSinkandRTCP()\" (in \"ServerMediaSubession\", and its subclasses \"OnDemandServerMediaSession\" and \"PassiveServerMediaSubsession\") to make its \'result\' arguments \"rtpSink\" and \"rtcp\" no longer \"const
*\". There was no real reason to make those \"const
*\".- update to 2023.11.07:
* In the class \"GenericMediaServer\", made the variables \"fServerMediaSessions\", \"fClientConnections\", and \"fClientSessions\" \'protected\' rather than \'private\', to allow subclasses to access them if desired.- update to 2023.10.30:
* Fixed a bug in \"deleteEventTrigger()\" that had accidentally been introduced during the change to \'event trigger\' implementation back in June.- update to 2023.07.24:
* Updated the event trigger implementation once again, to allow for the possibility of developers redefining MAX_NUM_EVENT_TRIGGERS (it must always be <= the number of bits in an \"EventTriggerId\", though.- update to 2023.06.20:
* Updated the event trigger implementation again - in the case where \"NO_STD_LIB\" is defined. In this case, \"fTriggersAwaitingHandling\" is implemented as an array of \"Boolean volatile\"s, rather than as a 32-bit bitmap. This should make \'race conditions\' less likely even if \"NO_STD_LIB\" is defined (though you should use the preferred, default implementation - that uses an array of \"std::atomic_flag\"s - if possible).- update to 2023.06.16:
* Changed the (default) implementation of \'event triggers\' in \"BasicTaskScheduler\" to implement \"fTriggersAwaitingHandling\" using \"std:atomic_flag\"s, rather than as a bitmap. This should overcome \'race conditions\' that some users experienced when calling \"triggerEvent()\" from a non-LIVE555 thread.
* Note that this is the first time the LIVE555 code has required the C++ standard library. (If you cannot use the C++ standard library, then you can compile the code - but getting the old behavior - by defining \"NO_STD_LIB\".)
* Minor change to \"RTSPCommon.cpp\" to overcome a compilation error in XCode on Mac OS X.- update to 2023.06.14:
* Fixed a bug in the Matroska file parsing code that could sometimes cause a \'use after free\' error. (bsc#1218758, CVE-2023-20573)- update to 2023.06.10:
* Minor change to \"GroupsockHelper.cpp\" to overcome a compilation error in XCode on Mac OS X.- update to 2023.06.08:
* Updated the \"dateHeader()\" function in \"RTSPCommon.cpp\" to use \"gmtime_r()\" instead of the older, non-thread-safe \"gmtime()\".- Applied workarounds for the build error with atomic_flag test
* Mon May 29 2023 Dirk Müller - update to 2023.5.10:
* Fixed a minor memory leak in the \"RTSPServer\" code.
* Calls to \"send()\" and \"sendto()\" now explicitly take \"MSG_NOSIGNAL\" rather than 0 as the \'flags\' parameter. In most systems, 0 seems to work, but apparently not in Debian Linux.
* Sat Jan 21 2023 Dirk Müller - update to 2023.01.19: - By default, we no longer compile \"groupsock/NetAddress.cpp\" for Windows to use \"gethostbyname()\", because of a report that this breaks IPv6 name resolution.
* Mon Jan 16 2023 Dirk Müller - update to 2023.01.11:
* Updated the \"BasicTaskScheduler\"/\"DelayQueue\" implementation to make the \'token counter\' a field of the task scheduler object, rather than having it be a static variable. This avoids potential problems if an application uses more than one thread (with each thread having its own task scheduler).
* Fri Dec 02 2022 Dirk Müller - update to 2022.12.01: - Yet another fix to the previous fix for RTSP-over-HTTP streaming. - The previous version\'s fix to \"RTSPClient\" (for RTSP-over-HTTP streaming) was incomplete. This should fix it for real. - Fixed a bug in \"RTSPClient\" that would cause RTSP-over-HTTP streaming over TLS to sometimes fail. (Thanks to Johannes Gajdosik for reporting this.) - Fixed a bug that would cause a RTSP server to use an incorrect URL if it accepted connections via TLS, but
*without
* streaming SRTP.
* Tue Nov 22 2022 Dirk Müller - update to 2022.11.19: - Added a new global variable \"ReceivingInterfaceAddr6\" (analogous to the existing variable \"ReceivingInterfaceAddr\" for IPv4) to allow applications to optionally change the default receiving address for IPv6.
* Sun Oct 02 2022 Dirk Müller - update to 2022.10.01: - Updated the previous revision so that the virtual function \"specialHandlingOfAuthenticationFailure()\" is now called only if there is an actual authentication failure - not on the first time that we send back a \"401 Unauthorized\" response. - Added a new virtual function \"specialHandlingOfAuthenticationFailure()\" to \"RTSPServer\" to allow a subclassed \"RTSPServer\" to take special action (e.g., statistics logging) whenever an authentication failure occurs.
* Fri Jul 22 2022 Dirk Müller - update to 2022.07.14:
* use SHA-1 rather than MD5 to hash the latest tarball of our code
* Fri Jun 24 2022 Dominique Leuenberger - Update to version 2022.06.16: + Both our RTSP client and RTSP server implementations now support (optional) RTSP-over-HTTPS streaming, when RTSP-over-TLS would otherwise be available.- Changes from version 2022.06.14: + Added optional support (via #ifdefs) to the \"testOnDemandRTSPServer\" demo application for streaming via RTSPS (RTSP-over-TLS) and optionally SRTP (encrypted RTP/RTCP). To use this, you would need to define SERVER_USE_TLS, and PATHNAME_TO_CERTIFICATE_FILE and PATHNAME_TO_PRIVATE_KEY_FILE.
* Wed May 04 2022 Christophe Giboudeaux - Update to 2022.04.26:
* Ensure that we don\'t call \"delete[]\" on an uninitialized pointer.- Changes from version 2022.04.15:
* Fixed a \"fprintf()\" argument-order-evaluation bug in the \"mikeyParse\" demo application.- Changes from version 2022.04.12:
* Updated the \"openRTSP\" application (RTSP command-line client) to add an option \'-L\', meaning: receive only an \"application\" (e.g., \'metadata\') track, if present, outputting the data to \'stdout\'.