File 0923-Add-appup-for-diameter-2.2.5.patch of Package erlang

From fc187d4b68489925e8e9fc42bb04a05ca3ae5e21 Mon Sep 17 00:00:00 2001
From: Anders Svensson <anders@erlang.org>
Date: Wed, 9 Mar 2022 09:52:17 +0100
Subject: [PATCH] Add appup for diameter 2.2.5

The parent commit modified modules in diameter, but since there have
been no other changes in diameter there's no appup entry that would let
the commit pass unnoticed: our release machinery forces a version bump
for OTP 24.3, and that requires an appup entry for upgrade to be
possible (and for our system upgrade suite to pass), even though none of
the modified modules are in the app file. This all seems a little
questionable, but add an appup entry for the noop upgrade to pacify the
machinery.

The changes in diameter are to info/debug modules, not released code.
That is, despite the version bump, there's no change to released modules
in diameter.
---
 lib/diameter/src/diameter.appup.src | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/lib/diameter/src/diameter.appup.src b/lib/diameter/src/diameter.appup.src
index e6379cd78a..6fa06d48a2 100644
--- a/lib/diameter/src/diameter.appup.src
+++ b/lib/diameter/src/diameter.appup.src
@@ -74,7 +74,8 @@
                {update, diameter_sctp}]},
  {"2.2.2",    [{load_module, diameter},            %% 22.2.8
                {update, diameter_sctp}]},
- {"2.2.3",    [{update, diameter_sctp}]}           %% 22.3
+ {"2.2.3",    [{update, diameter_sctp}]},          %% 22.3
+ {"2.2.4",    []}                                  %% 23.3.4
  ],
  [
   {"0.9",     [{restart_application, diameter}]},
@@ -130,6 +131,7 @@
                {update, diameter_sctp}]},
   {"2.2.2",   [{load_module, diameter},
                {update, diameter_sctp}]},
-  {"2.2.3",   [{update, diameter_sctp}]}
+  {"2.2.3",   [{update, diameter_sctp}]},
+  {"2.2.4",   []}
  ]
 }.
-- 
2.34.1