From: acidvegas <acidvegas@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: incus: update to 0.6.0
Date: Wed, 20 Mar 2024 18:21:37 +0100 [thread overview]
Message-ID: <20240320172137.ACC49228B1@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49265@inbox.vuxu.org>
[-- 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)
next prev parent reply other threads:[~2024-03-20 17:21 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 0:02 [PR PATCH] " cmspam
2024-03-13 1:04 ` cmspam
2024-03-13 1:06 ` cmspam
2024-03-13 1:06 ` cmspam
2024-03-13 1:06 ` cmspam
2024-03-13 1:13 ` cmspam
2024-03-18 22:09 ` dkwo
2024-03-19 2:56 ` acidvegas
2024-03-19 4:25 ` cmspam
2024-03-20 13:13 ` ahesford
2024-03-20 17:19 ` acidvegas
2024-03-20 17:19 ` acidvegas
2024-03-20 17:20 ` acidvegas
2024-03-20 17:21 ` acidvegas [this message]
2024-03-20 17:22 ` acidvegas
2024-03-24 11:39 ` cmspam
2024-03-24 11:39 ` cmspam
2024-03-26 2:03 ` cmspam
2024-03-26 2:29 ` ahesford
2024-03-26 2:37 ` vxfemboy
2024-03-26 2:39 ` cmspam
2024-03-26 2:41 ` ahesford
2024-03-26 2:44 ` acidvegas
2024-03-26 2:56 ` [PR PATCH] [Updated] " cmspam
2024-03-26 2:59 ` cmspam
2024-03-26 3:00 ` cmspam
2024-03-26 3:40 ` cmspam
2024-03-26 3:41 ` cmspam
2024-03-26 3:41 ` cmspam
2024-03-26 3:44 ` cmspam
2024-03-26 3:45 ` cmspam
2024-03-26 3:46 ` cmspam
2024-03-26 3:46 ` cmspam
2024-03-26 3:49 ` cmspam
2024-03-26 3:49 ` cmspam
2024-03-26 3:50 ` cmspam
2024-03-26 3:52 ` cmspam
2024-03-26 3:53 ` cmspam
2024-03-26 10:42 ` [PR PATCH] [Merged]: " ahesford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240320172137.ACC49228B1@inbox.vuxu.org \
--to=acidvegas@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).