From mboxrd@z Thu Jan  1 00:00:00 1970
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: nmap PAK_VER bumped from 15 to 16 in three separate commits
Date: Tue, 08 Aug 2023 21:05:17 +0200
Message-ID: <a74c1819-f7f3-470e-97e1-ad5db3be7980@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3080902940800698337=="
List-Id: <development.lists.ipfire.org>

--===============3080902940800698337==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi All,

Don't know if git will cope with this or not but I submitted an nmap/ncat upd=
ate which was merged on 24th July and incremented the PAK_VER from 15 to 16

https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommit;h=3Da6b7832024ca58d689e=
59ff0a12442f573d2dfff

Today Matthias submitted a patch to increment the PAK_VER of nmap from 15 to =
16.

Then a bit later Michael raised a patch on CU177 that incremented the PAK_VER=
 of nmap from 15 to 16.


So there are three commits each of which increment the PAK_VER of the same pa=
ckage in the identical way.


Regards,

Adolf.


--===============3080902940800698337==--