From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: nmap PAK_VER bumped from 15 to 16 in three separate commits Date: Fri, 11 Aug 2023 13:00:30 +0200 Message-ID: <9BE0B5F6-1089-4334-8FC0-BE6E56353CB0@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8183249430572977354==" List-Id: --===============8183249430572977354== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello Adolf, Thank you for highlighting this. This can indeed become a problem, so I will make sure and once again bump the= version in next, so that people will see the updated version and get the cha= nges that have been submitted recently, but in master, people will get the re= build of the latest version. That should hopefully do it. Best, -Michael > On 8 Aug 2023, at 21:05, Adolf Belka wrote: >=20 > Hi All, >=20 > Don't know if git will cope with this or not but I submitted an nmap/ncat u= pdate which was merged on 24th July and incremented the PAK_VER from 15 to 16 >=20 > https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommit;h=3Da6b7832024ca58d68= 9e59ff0a12442f573d2dfff >=20 > Today Matthias submitted a patch to increment the PAK_VER of nmap from 15 t= o 16. >=20 > Then a bit later Michael raised a patch on CU177 that incremented the PAK_V= ER of nmap from 15 to 16. >=20 >=20 > So there are three commits each of which increment the PAK_VER of the same = package in the identical way. >=20 >=20 > Regards, >=20 > Adolf. >=20 --===============8183249430572977354==--