[pve-devel] [PATCH container] setup: add kali-rolling in supported releases

[pve-devel] [PATCH container] setup: add kali-rolling in supported releases

[Oguz Bektas]

for our setup purposes, it's the same as bullseye since it's following a
rolling release model.

Signed-off-by: Oguz Bektas <o.bektas@proxmox.com>
---
 src/PVE/LXC/Setup/Debian.pm | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/PVE/LXC/Setup/Debian.pm b/src/PVE/LXC/Setup/Debian.pm
index 13a2d55..0cb01c4 100644
--- a/src/PVE/LXC/Setup/Debian.pm
+++ b/src/PVE/LXC/Setup/Debian.pm
@@ -23,6 +23,7 @@ sub new {
     $version = 9.1 if $version eq 'stretch/sid';
     $version = 10 if $version eq 'buster/sid';
     $version = 11 if $version eq 'bullseye/sid';
+    $version = 11 if $version eq 'kali-rolling';
 
     die "unable to parse version info '$version'\n"
 	if $version !~ m/^(\d+(\.\d+)?)(\.\d+)?/;
-- 
2.20.1

[pve-devel] applied: [PATCH container] setup: add kali-rolling in supported releases

[Thomas Lamprecht]

On 01.09.20 12:44, Oguz Bektas wrote:
> for our setup purposes, it's the same as bullseye since it's following a
> rolling release model.
> 
> Signed-off-by: Oguz Bektas <o.bektas@proxmox.com>
> ---
>  src/PVE/LXC/Setup/Debian.pm | 1 +
>  1 file changed, 1 insertion(+)
> 
>

applied, thanks! Albeit it could make sense to have a special "sid" version
and map this then also to "sid", avoiding the need to update it again?