nmap PAK_VER bumped from 15 to 16 in three separate commits

nmap PAK_VER bumped from 15 to 16 in three separate commits

[Adolf Belka]

[-- Attachment #1: Type: text/plain, Size: 585 bytes --]

Hi All,

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

https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=a6b7832024ca58d689e59ff0a12442f573d2dfff

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 package in the identical way.


Regards,

Adolf.

Re: nmap PAK_VER bumped from 15 to 16 in three separate commits

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]

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 changes that have been submitted recently, but in master, people will get the rebuild of the latest version.

That should hopefully do it.

Best,
-Michael

> On 8 Aug 2023, at 21:05, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi All,
> 
> Don't know if git will cope with this or not but I submitted an nmap/ncat update which was merged on 24th July and incremented the PAK_VER from 15 to 16
> 
> https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=a6b7832024ca58d689e59ff0a12442f573d2dfff
> 
> 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 package in the identical way.
> 
> 
> Regards,
> 
> Adolf.
>