Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lxd-to-incus fails on void linux #49542

Closed
cmspam opened this issue Mar 26, 2024 · 1 comment · Fixed by #49265
Closed

lxd-to-incus fails on void linux #49542

cmspam opened this issue Mar 26, 2024 · 1 comment · Fixed by #49265
Labels
bug Something isn't working needs-testing Testing a PR or reproducing an issue needed

Comments

@cmspam
Copy link
Contributor

cmspam commented Mar 26, 2024

Is this a new report?

Yes

Package(s) Affected

incus-0.5.1

Does a report exist for this bug with the project's home (upstream) and/or another distro?

lxc/incus#625
lxc/incus#511

Expected behaviour

The server should be found

Actual behaviour

"Error: No target server could be found"

Steps to reproduce

void linux support was added to incus 0.6 upstream, but incus version is stuck at 0.5.1.
This PR updates incus to 0.6 and fixes the issue, but remains unmerged as of yet:
#49265

@cmspam cmspam added bug Something isn't working needs-testing Testing a PR or reproducing an issue needed labels Mar 26, 2024
@ahesford
Copy link
Member

The fact that the version packaged by Void lacks features found in later versions isn't a bug, and we have mechanisms to track outdated versions that don't require opening issues. In fact, filing issues to complain of outdated packages just distracts maintainers and buries real issues m, so please refrain from doing so in the future.

@ahesford ahesford closed this as not planned Won't fix, can't repro, duplicate, stale Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-testing Testing a PR or reproducing an issue needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants