Follow-up to #237. Assigning ssh-client was refused: ssh-client and sshd both declare the package "openssh" (a package has one owning module). sshd already owns openssh on all four nodes, and owning it here was wrong anyway — unassigning ssh-client would remove the package sshd serves from.
Verified: mesh-controller main go test ./internal/catalogue/ passes with this catalogue beside it.
Follow-up to #237. Assigning ssh-client was refused: `ssh-client and sshd both declare the package "openssh"` (a package has one owning module). sshd already owns openssh on all four nodes, and owning it here was wrong anyway — unassigning ssh-client would remove the package sshd serves from.
Verified: mesh-controller main `go test ./internal/catalogue/` passes with this catalogue beside it.
A package has one owning module, and sshd already owns openssh on every node — assigning
ssh-client was refused for both declaring it, and the refusal left every node unresolvable
until it was unassigned. Owning it was wrong besides: unassigning ssh-client would have
removed the package sshd serves from. The client binary ships in the package sshd holds.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Follow-up to #237. Assigning ssh-client was refused:
ssh-client and sshd both declare the package "openssh"(a package has one owning module). sshd already owns openssh on all four nodes, and owning it here was wrong anyway — unassigning ssh-client would remove the package sshd serves from.Verified: mesh-controller main
go test ./internal/catalogue/passes with this catalogue beside it.