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
neither (group-spec .... :packager :aptitude) nor (node-spec .... :packager :apt) seem to have any effect on specifying the packager to use for a node.
We have many instances for which pallet does not detect the packager, which we can't use with the latest version of pallet which now ignores setting the packager explicitly.
the workaround for this is to hack the default packager to be :apt
Pallet should now be dynamically determining the packager. It runs an internal :pallet/os phase to achieve this. Is the phase not getting run, or is it failing to detect the os correctly?
I don't yet know if it is failing because it is not running or it runs and fails?
This bug it about the inability to override it's decision. If overriding it is not allowed then the :packager key should be removed from group-spec. If it is allowed then it would be nice if the :packager key was used instead of the calculated result.
neither (group-spec .... :packager :aptitude) nor (node-spec .... :packager :apt) seem to have any effect on specifying the packager to use for a node.
We have many instances for which pallet does not detect the packager, which we can't use with the latest version of pallet which now ignores setting the packager explicitly.
the workaround for this is to hack the default packager to be :apt
(alter-var-root (var pallet.compute/packager-map) assoc {:os :unrecognized} :apt)
The text was updated successfully, but these errors were encountered: