[PR PATCH] incus: update to 0.6.0

[PR PATCH] incus: update to 0.6.0

[cmspam]

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

There is a new pull request by cmspam against master on the void-packages repository

https://github.com/cmspam/void-packages patch-1
https://github.com/void-linux/void-packages/pull/49265

incus: update to 0.6.0
Updated incus to version 0.6.0

A simple update. Incus has been stuck at 0.5.1 on Void for a pretty long time, so I propose updating to 0.6.0.

<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **NO**


<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


A patch file from https://github.com/void-linux/void-packages/pull/49265.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-patch-1-49265.patch --]
[-- Type: text/x-diff, Size: 1066 bytes --]

From 310c369ddbef60c56f3eb93a9226b9bfe893c4fd Mon Sep 17 00:00:00 2001
From: cmspam <charlesmillerspam@gmail.com>
Date: Wed, 13 Mar 2024 08:59:36 +0900
Subject: [PATCH] incus: update to 0.6.0

Updated incus to version 0.6.0
---
 srcpkgs/incus/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/incus/template b/srcpkgs/incus/template
index 3d63abe98a3c46..cb0b5ef046a07b 100644
--- a/srcpkgs/incus/template
+++ b/srcpkgs/incus/template
@@ -1,6 +1,6 @@
 # Template file for 'incus'
 pkgname=incus
-version=0.5.1
+version=0.6.0
 revision=1
 build_style=go
 go_import_path=github.com/lxc/incus
@@ -20,7 +20,7 @@ maintainer="dkwo <npiazza@disroot.org>"
 license="Apache-2.0"
 homepage="https://linuxcontainers.org/incus"
 distfiles="https://github.com/lxc/incus/archive/refs/tags/v${version}.tar.gz"
-checksum=ca757fa69272650fc2a3aab73d27b11cee48f3872115b664f234af74cc6684ec
+checksum=9bbce9ae95b40be4bd11116a97f422ecd2adf2915a2c0b6828fa34435de756d2
 system_groups="_incus-admin _incus"
 make_dirs="
  /var/lib/incus 0755 root root

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-1992909882

Comment:
I have now tested it to the extent of initializing, creating a network bridge and an instance, everything is working.

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-1992909882

Comment:
I have now tested it to the extent of building, initializing, creating a network bridge and an instance, everything is working.

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-1992909882

Comment:
I have now tested it (x86_64 glibc) to the extent of building, initializing, creating a network bridge and an instance, everything is working.

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-1992909882

Comment:
I have now tested it (x86_64 glibc) to the extent of building, initializing, creating a network bridge and an instance, everything is working normally.

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-1992909882

Comment:
I have now tested it (x86_64 glibc) to the extent of building, initializing, creating a network bridge and launching a container instance, everything is working normally.

Re: incus: update to 0.6.0

[dkwo]

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

New comment by dkwo on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2005133285

Comment:
looks good to me

Re: incus: update to 0.6.0

[acidvegas]

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

New comment by acidvegas on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2005655230

Comment:
🕛🕧🕐🕜🕑🕝🕒

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2005729929

Comment:
If anything more is necessary for a merge, let me know.
I'm worried this package will fall behind.

Re: incus: update to 0.6.0

[ahesford]

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

New comment by acidvegas on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2005655230

Comment:
🕛🕧🕐🕜🕑🕝🕒

Re: incus: update to 0.6.0

[acidvegas]

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

New comment by acidvegas on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2010136116

Comment:
No offense and all but [Canonical](https://ubuntu.com/community/governance/canonical) has taken some serious hostile community actions against LXD as of recent, and well.....LXD is pretty much useless now for some. You can't even spin up a Debian container with it anymore. As of 03/15 `LXD 5.20+ users running on any distribution will completely lose access`

**Everyone** is in the process **right now** of transitioning to Inucs from LXD. The current version in Void is broken with the `lxd-to-incus` package failing for anyone using Void linux....

Can we prioritize this merge or something.....?

Re: incus: update to 0.6.0

[acidvegas]

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

New comment by acidvegas on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2010136116

Comment:
No offense and all but [Canonical](https://ubuntu.com/community/governance/canonical) has taken some serious hostile community actions against LXD as of recent, and well.....LXD is pretty much useless now for some. You can't even spin up a Debian container with it anymore. As of 03/15 `LXD 5.20+ users running on any distribution will completely lose access`

**Everyone** is in the process **right now** of transitioning to LXD to Incus. The current version in Void is broken with the `lxd-to-incus` package failing for anyone using Void linux....

Can we prioritize this merge or something.....?

Re: incus: update to 0.6.0

[acidvegas]

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

New comment by acidvegas on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2010136116

Comment:
No offense and all but [Canonical](https://ubuntu.com/community/governance/canonical) has taken some serious hostile community actions against LXD as of recent, and well.....LXD is pretty much useless now for some. You can't even spin up a Debian container with it anymore. As of 03/15 `LXD 5.20+ users running on any distribution will completely lose access`

**Everyone** is in the process **right now** of transitioning from LXD to Incus. The current version in Void is broken with the `lxd-to-incus` package failing for anyone using Void linux....

Can we prioritize this merge or something.....?

Re: incus: update to 0.6.0

[acidvegas]

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

New comment by acidvegas on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2010136116

Comment:
No offense and all but [Canonical](https://ubuntu.com/community/governance/canonical) has taken some serious hostile community actions against LXD as of recent, and well.....LXD is pretty much useless now for some. You can't even spin up a Debian container with it anymore. As of 03/15 `LXD 5.20+ users running on any distribution will completely lose access`

**Everyone** is in the process **right now** of transitioning from LXD to Incus. The current version in Void is broken with the `lxd-to-incus` package failing for anyone using Void linux....

Can we prioritize this merge or something.....? The latest version fixes this issue for all Void users.... [625](https://github.com/lxc/incus/issues/625)

Re: incus: update to 0.6.0

[acidvegas]

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

New comment by acidvegas on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2010136116

Comment:
 [Canonical](https://ubuntu.com/community/governance/canonical) has taken some serious hostile community actions against LXD as of recent, and well.....LXD is pretty much useless now for some. You can't even spin up a Debian container with it anymore. As of 03/15 `LXD 5.20+ users running on any distribution will completely lose access`

**Everyone** is in the process **right now** of transitioning from LXD to Incus. The current version in Void is broken with the `lxd-to-incus` package failing for anyone using Void linux....

No offense and all but can we prioritize this merge or something.....? The latest version fixes this issue for all Void users.... [625](https://github.com/lxc/incus/issues/625)

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2016780627

Comment:
Pinging @ahesford as he was the one who initially merged the package. Please let me know if anything else is necessary to merge this.

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2016780627

Comment:
Pinging @ahesford as he was the one who initially merged incus. Please let me know if anything else is necessary to merge this.

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2019252492

Comment:
> [Canonical](https://ubuntu.com/community/governance/canonical) has taken some serious hostile community actions against LXD as of recent, and well.....LXD is pretty much useless now for some. You can't even spin up a Debian container with it anymore. As of 03/15 `LXD 5.20+ users running on any distribution will completely lose access`
> 
> **Everyone** is in the process **right now** of transitioning from LXD to Incus. The current version in Void is broken with the `lxd-to-incus` package failing for anyone using Void linux....
> 
> No offense and all but can we prioritize this merge or something.....? The latest version fixes this issue for all Void users.... [625](https://github.com/lxc/incus/issues/625)

I have added your issue to void and linked it to this PR, to hopefully get it merged so that others don't have the same issue in the future:

https://github.com/void-linux/void-packages/issues/49542

Re: incus: update to 0.6.0

[ahesford]

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

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2019273179

Comment:
Please drop the redundant second line in your commit message.

I merged the original PR because it had the approval of others, but I don't use incus and don't really know the details of the lxd/incus debacle. Because the package manager approves the update, I'm happy to merge once the commit message is cleaned up.

We could do with fewer breathless protestations about packages falling behind when the version in the repo is only two months old and the version you're updating to was released last month. If you  want bleeding-edge packages, there are other distributions to fulfill that desire.

Re: incus: update to 0.6.0

[vxfemboy]

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

New comment by vxfemboy on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2019278814

Comment:
sometimes when i get mad over a 2 line commit i like to slam my c0ck in the fridge door 10 times just to cool it off, often times i slip on a ice cube after then fall on my back shattering my spine and crying, this is all due to a 2 line commit message... maybe i should throw my computer in a lake

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2019280204

Comment:
> Please drop the redundant second line in your commit message.
> 
> I merged the original PR because it had the approval of others, but I don't use incus and don't really know the details of the lxd/incus debacle. Because the package manager approves the update, I'm happy to merge once the commit message is cleaned up.
> 
> We could do with fewer breathless protestations about packages falling behind when the version in the repo is only two months old and the version you're updating to was released last month. If you want bleeding-edge packages, there are other distributions to fulfill that desire.

There is an important void-specific fix implemented by this update, hence the breathless protestations. That said, I'm more than happy not to try to fix things in a community where my help is not wanted.  I'll fix this commit message, and let others deal with any other void/incus issues in the future.

Re: incus: update to 0.6.0

[ahesford]

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

New comment by vxfemboy on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2019278814

Comment:
sometimes when i get mad over a 2 line commit i like to slam my c0ck in the fridge door 10 times just to cool it off, often times i slip on a ice cube after then fall on my back shattering my spine and crying, this is all due to a 2 line commit message... maybe i should throw my computer in a lake

Re: incus: update to 0.6.0

[acidvegas]

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

New comment by acidvegas on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2019284064

Comment:
@ahesford way to run off a contributor smh...

Re: [PR PATCH] [Updated] incus: update to 0.6.0

[cmspam]

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

There is an updated pull request by cmspam against master on the void-packages repository

https://github.com/cmspam/void-packages patch-1
https://github.com/void-linux/void-packages/pull/49265

incus: update to 0.6.0
Updated incus to version 0.6.0

A simple update. Incus has been stuck at 0.5.1 on Void for a pretty long time, so I propose updating to 0.6.0.

fixes #49542

<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**


<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


A patch file from https://github.com/void-linux/void-packages/pull/49265.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-patch-1-49265.patch --]
[-- Type: text/x-diff, Size: 1035 bytes --]

From 3887286f1ade092d02b275ffb7fec690ac638da4 Mon Sep 17 00:00:00 2001
From: cmspam <charlesmillerspam@gmail.com>
Date: Wed, 13 Mar 2024 08:59:36 +0900
Subject: [PATCH] incus: update to 0.6.0

---
 srcpkgs/incus/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/incus/template b/srcpkgs/incus/template
index 3d63abe98a3c46..cb0b5ef046a07b 100644
--- a/srcpkgs/incus/template
+++ b/srcpkgs/incus/template
@@ -1,6 +1,6 @@
 # Template file for 'incus'
 pkgname=incus
-version=0.5.1
+version=0.6.0
 revision=1
 build_style=go
 go_import_path=github.com/lxc/incus
@@ -20,7 +20,7 @@ maintainer="dkwo <npiazza@disroot.org>"
 license="Apache-2.0"
 homepage="https://linuxcontainers.org/incus"
 distfiles="https://github.com/lxc/incus/archive/refs/tags/v${version}.tar.gz"
-checksum=ca757fa69272650fc2a3aab73d27b11cee48f3872115b664f234af74cc6684ec
+checksum=9bbce9ae95b40be4bd11116a97f422ecd2adf2915a2c0b6828fa34435de756d2
 system_groups="_incus-admin _incus"
 make_dirs="
  /var/lib/incus 0755 root root

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2019295118

Comment:
@ahesford The second line in the commit message is now dropped.
I hope that my enthusiasm for incus's integration into void hasn't put a bad taste in the void maintainers' mouths for the project -- it's extremely useful, and should help many people who want an integrated system for managing containers and VMs.
I will not be contributing to it in the future, but I sincerely hope that others do.

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2019295118

Comment:
@ahesford The second line in the commit message is now dropped.
I hope that my enthusiasm for incus's integration into void hasn't put a bad taste in the void maintainers' mouths for the project -- it's extremely useful, and should help many people who want an integrated system for managing containers and VMs.
I will not be contributing here in the future, but I sincerely hope that others do.

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2019280204

Comment:
> Please drop the redundant second line in your commit message.
> 
> I merged the original PR because it had the approval of others, but I don't use incus and don't really know the details of the lxd/incus debacle. Because the package manager approves the update, I'm happy to merge once the commit message is cleaned up.
> 
> We could do with fewer breathless protestations about packages falling behind when the version in the repo is only two months old and the version you're updating to was released last month. If you want bleeding-edge packages, there are other distributions to fulfill that desire.

There is an important void-specific fix implemented by this update, hence the breathless protestations. Initially I submitted this PR because Incus was out of date. I then saw an issue with void specifically, that was fixed with this update, and thought that because of the void-specificity of the issue/fix this might want to be merged sooner than later.

This is not an issue of wanting bleeding edge features. It's an issue of wanting void-specific functionality added upstream to cover for a lack thereof, to be available sooner rather than later. There is a cut-off date for linuxcontainers image support for LXD, and many other reasons that migrations to incus need to be made quickly, and this particular version of incus is instrumental in enabling that for void users, because the migration tool was broken for void specifically up until this version, which specifically fixes it for void.

That said, I'm more than happy not to try to push fixes or updates along in a community where my help is not wanted.  I'll fix this commit message, and let others deal with any other void/incus issues in the future.

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2019280204

Comment:
> Please drop the redundant second line in your commit message.
> 
> I merged the original PR because it had the approval of others, but I don't use incus and don't really know the details of the lxd/incus debacle. Because the package manager approves the update, I'm happy to merge once the commit message is cleaned up.
> 
> We could do with fewer breathless protestations about packages falling behind when the version in the repo is only two months old and the version you're updating to was released last month. If you want bleeding-edge packages, there are other distributions to fulfill that desire.

There is an important void-specific fix implemented by this update, hence the breathless protestations. Initially I submitted this PR because Incus was out of date. I then saw an issue with void specifically, that was fixed with this update, and thought that because of the void-specificity of the issue/fix this might want to be merged sooner than later, and attention needed to be drawn to it.

This is not an issue of wanting bleeding edge features. It's an issue of wanting void-specific functionality added upstream to cover for a lack thereof, to be available sooner rather than later. There is a cut-off date for linuxcontainers image support for LXD, and many other reasons that migrations to incus need to be made quickly, and this particular version of incus is instrumental in enabling that for void users, because the migration tool was broken for void specifically up until this version, which specifically fixes it for void.

That said, I'm more than happy not to try to push fixes or updates along in a community where my help is not wanted.  I'll fix this commit message, and let others deal with any other void/incus issues in the future.

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2019280204

Comment:
> Please drop the redundant second line in your commit message.
> 
> I merged the original PR because it had the approval of others, but I don't use incus and don't really know the details of the lxd/incus debacle. Because the package manager approves the update, I'm happy to merge once the commit message is cleaned up.
> 
> We could do with fewer breathless protestations about packages falling behind when the version in the repo is only two months old and the version you're updating to was released last month. If you want bleeding-edge packages, there are other distributions to fulfill that desire.

There is an important void-specific fix implemented by this update, hence the breathless protestations. Initially I submitted this PR because Incus was out of date. I then saw an issue with void specifically, that was fixed with this update, and thought that because of the void-specificity of the issue/fix this might want to be merged sooner than later, and attention needed to be drawn to it.

This is not an issue of wanting bleeding edge features. It's an issue of wanting void-specific functionality added upstream to cover for a lack thereof, to be available in void before it's too late for people to have an easy migration path. There is a cut-off date for linuxcontainers image support for LXD, and many other reasons that migrations to incus need to be made quickly, and this particular version of incus is instrumental in enabling that for void users, because the migration tool was broken for void specifically up until this version, which specifically fixes it for void.

That said, I'm more than happy not to try to push fixes or updates along in a community where my help is not wanted.  I'll fix this commit message, and let others deal with any other void/incus issues in the future.

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2019280204

Comment:

> We could do with fewer breathless protestations about packages falling behind when the version in the repo is only two months old and the version you're updating to was released last month. If you want bleeding-edge packages, there are other distributions to fulfill that desire.

There is an important void-specific fix implemented by this update, hence the breathless protestations. Initially I submitted this PR because Incus was out of date. I then saw an issue with void specifically, that was fixed with this update, and thought that because of the void-specificity of the issue/fix this might want to be merged sooner than later, and attention needed to be drawn to it.

This is not an issue of wanting bleeding edge features. It's an issue of wanting void-specific functionality added upstream to cover for a lack thereof, to be available in void before it's too late for people to have an easy migration path. There is a cut-off date for linuxcontainers image support for LXD, and many other reasons that migrations to incus need to be made quickly, and this particular version of incus is instrumental in enabling that for void users, because the migration tool was broken for void specifically up until this version, which specifically fixes it for void.

That said, I'm more than happy not to try to push fixes or updates along in a community where my help is not wanted.  I don't run incus on void personally, and the push was to help others who do. I'll fix this commit message, and let others deal with any other void/incus issues in the future.

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2019280204

Comment:
> We could do with fewer breathless protestations about packages falling behind when the version in the repo is only two months old and the version you're updating to was released last month. If you want bleeding-edge packages, there are other distributions to fulfill that desire.

There is an important void-specific fix implemented by this update, hence the breathless protestations. Initially I submitted this PR because Incus was out of date. I then saw an issue with void specifically, that was fixed with this update, and thought that because of the void-specificity of the issue/fix this might want to be merged sooner than later, and attention needed to be drawn to it.

This is not an issue of wanting bleeding edge features. It's an issue of wanting void-specific functionality added upstream to cover for a lack thereof, to be available in void before it's too late for people to have an easy migration path. There is a cut-off date for linuxcontainers image support for LXD, and many other reasons that migrations to incus need to be made quickly, and this particular version of incus is instrumental in enabling that for void users, because the migration tool was broken for void specifically up until this version, which specifically fixes it for void.

That said, I'm more than happy not to try to push fixes or updates along in a community where my help is not wanted.  I don't run incus on void personally, and any urgency behind this PR was simply to help others who do. I'll fix this commit message, and let others deal with any other void/incus issues in the future.

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2019295118

Comment:
@ahesford The second line in the commit message is now dropped.
I hope that my enthusiasm for fixing incus's issues on void hasn't put a bad taste in the void maintainers' mouths for the project -- it's extremely useful, and should help many people who want an integrated system for managing containers and VMs.
I will not be contributing here in the future, but I sincerely hope that others do.

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2019295118

Comment:
@ahesford The second line in the commit message is now dropped.
I hope that my enthusiasm for incus on void hasn't put a bad taste in the void maintainers' mouths for the project -- it's extremely useful, and should help many people who want an integrated system for managing containers and VMs.
I will not be contributing here in the future, but I sincerely hope that others do.

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2019280204

Comment:
> We could do with fewer breathless protestations about packages falling behind when the version in the repo is only two months old and the version you're updating to was released last month. If you want bleeding-edge packages, there are other distributions to fulfill that desire.

There is an important void-specific fix implemented by this update, hence the breathless protestations. Initially I submitted this PR because Incus was out of date. I then saw an issue with void specifically, that was fixed with this update, and thought that because of the void-specificity of the issue/fix this might want to be merged sooner than later, and attention needed to be drawn to it.

This is not an issue of wanting bleeding edge features. It's an issue of wanting void-specific functionality added upstream to cover for a lack thereof, to be available in void before it's too late for people to have an easy migration path. There is a cut-off date for linuxcontainers image support for LXD, and many other reasons that migrations to incus need to be made quickly, and this particular version of incus is instrumental in enabling that for void users, because the migration tool was included, but not working for void specifically up until this version, which specifically fixes it for void.

That said, I'm more than happy not to try to push fixes or updates along in a community where my help is not wanted.  I don't run incus on void personally, and any urgency behind this PR was simply to help others who do. I'll fix this commit message, and let others deal with any other void/incus issues in the future.

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2019280204

Comment:
> We could do with fewer breathless protestations about packages falling behind when the version in the repo is only two months old and the version you're updating to was released last month. If you want bleeding-edge packages, there are other distributions to fulfill that desire.

There is an important void-specific fix implemented by this update, hence the breathless protestations. Initially I submitted this PR because Incus was out of date. I then saw an issue with void specifically, that was fixed with this update, and thought that because of the void-specificity of the issue/fix this might want to be merged sooner than later, and attention needed to be drawn to it.

This is not an issue of wanting bleeding edge features. It's an issue of wanting void-specific functionality added upstream to cover for a lack thereof, to be available in void before it's too late for people to have an easy migration path. There is a cut-off date for linuxcontainers image support for LXD, and many other reasons that migrations to incus need to be made quickly, and this particular version of incus is instrumental in enabling that for void users, because the migration tool was included, but not working for void specifically up until this version, which specifically fixes it for void via https://github.com/lxc/incus/pull/511/commits

That said, I'm more than happy not to try to push fixes or updates along in a community where my help is not wanted.  I don't run incus on void personally, and any urgency behind this PR was simply to help others who do. I'll fix this commit message, and let others deal with any other void/incus issues in the future.

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2019280204

Comment:
> We could do with fewer breathless protestations about packages falling behind when the version in the repo is only two months old and the version you're updating to was released last month. If you want bleeding-edge packages, there are other distributions to fulfill that desire.

There is an important void-specific fix implemented by this update, hence the breathless protestations. Initially I submitted this PR because Incus was out of date. I then saw an issue with void specifically, that was fixed with this update, and thought that because of the void-specificity of the issue/fix this might want to be merged sooner than later, and attention needed to be drawn to it.

This is not an issue of wanting bleeding edge features. It's an issue of wanting void-specific functionality added upstream to cover for a lack thereof, to be available in void before it's too late for people to have an easy migration path. There is a cut-off date for linuxcontainers image support for LXD, and many other reasons that migrations to incus need to be made quickly, and this particular version of incus is instrumental in enabling that for void users, because the migration tool was included, but not working for void specifically up until this version, which specifically enables it for void via https://github.com/lxc/incus/pull/511/commits

That said, I'm more than happy not to try to push fixes or updates along in a community where my help is not wanted.  I don't run incus on void personally, and any urgency behind this PR was simply to help others who do. I'll fix this commit message, and let others deal with any other void/incus issues in the future.

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2019280204

Comment:
> We could do with fewer breathless protestations about packages falling behind when the version in the repo is only two months old and the version you're updating to was released last month. If you want bleeding-edge packages, there are other distributions to fulfill that desire.

There is an important void-specific fix implemented by this update, hence the breathless protestations. Initially I submitted this PR because Incus was out of date. I then saw an issue with void specifically, that was fixed with this update, and thought that because of the void-specificity of the issue/fix this might want to be merged sooner than later, and attention needed to be drawn to it.

This is not an issue of wanting bleeding edge features. It's an issue of wanting void-specific functionality which was added upstream to be available in void itself before it's too late for people to have an easy migration path. There is a cut-off date for linuxcontainers image support for LXD, which means that migrations to incus need to be made quickly, and this particular version of incus is instrumental in enabling that for void users, because the migration tool was included, but not working for void specifically up until this version, which specifically enables it for void via https://github.com/lxc/incus/pull/511/commits

That said, I'm more than happy not to try to push fixes or updates along in a community where my help is not wanted.  I don't run incus on void personally, and any urgency behind this PR was simply to help others who do. I'll fix this commit message, and let others deal with any other void/incus issues in the future.

Re: incus: update to 0.6.0

[cmspam]

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

New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2019280204

Comment:
> We could do with fewer breathless protestations about packages falling behind when the version in the repo is only two months old and the version you're updating to was released last month. If you want bleeding-edge packages, there are other distributions to fulfill that desire.

There is an important void-specific fix implemented by this update, hence the breathless protestations. Initially I submitted this PR because Incus was out of date. I then saw an issue with void specifically, that was fixed with this update, and thought that because of the void-specificity of the issue/fix this might want to be merged sooner than later, and attention needed to be drawn to it.

This is not an issue of wanting bleeding edge features. It's an issue of wanting void-specific functionality which was added upstream to be available in void itself before it's too late for people to have an easy migration path. There is a cut-off date for linuxcontainers image support for LXD, which means that migrations to incus need to be made quickly, and this particular version of incus is instrumental in enabling that for void users, because the migration tool was included, but not working for void specifically up until this version, which specifically enables it for void via https://github.com/lxc/incus/pull/511/commits

That said, I'm more than happy not to try to push fixes or updates along in a community where it is not wanted.  But I feel that you may not have fully understood the issue this PR solves before your comment, perhaps, or you may not have made it. I don't run incus on void personally, and any urgency behind this PR was simply to help others who do. I'll fix this commit message, and let others deal with any other void/incus issues in the future.

Re: [PR PATCH] [Merged]: incus: update to 0.6.0

[ahesford]

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

There's a merged pull request on the void-packages repository

incus: update to 0.6.0
https://github.com/void-linux/void-packages/pull/49265

Description:
Updated incus to version 0.6.0

A simple update. Incus has been stuck at 0.5.1 on Void for a pretty long time, so I propose updating to 0.6.0.

fixes #49542

<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**


<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->