You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
lxd-to-incus in tag incus-0.1 reports version 5.16. This is because lxd-to-incus is a completely separate go package and its parsing of the incus version is locked to what go.sum has.
Steps to reproduce
Clone repo
cd cmd/lxd-to-incus
go build ./.
./lxd-to-incus --version
5.16
Other
I'm attempting to finalize packaging incus for nixpkgs. Am I correct to assume that this should be 0.1 to match the incus version? Would it be better to maybe version it on its own? Since it's using go packages for all the incus dependencies, does it benefit from being in this repo?
The text was updated successfully, but these errors were encountered:
It needs to stay in the repo so it can access the infernal packages but indeed will need a bit of tweaking to get the correct version as there's otherwise a bit of a chicken and egg problem.
The reason for the separate gomod is that we don't want the migration tool to cause the main gomod to include all of the LXD packages.
Issue description
lxd-to-incus in tag incus-0.1 reports version 5.16. This is because lxd-to-incus is a completely separate go package and its parsing of the incus version is locked to what go.sum has.
Steps to reproduce
5.16
Other
I'm attempting to finalize packaging incus for nixpkgs. Am I correct to assume that this should be 0.1 to match the incus version? Would it be better to maybe version it on its own? Since it's using go packages for all the incus dependencies, does it benefit from being in this repo?
The text was updated successfully, but these errors were encountered: