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
In some cases, a flox upgrade will preserve derivations of all packages, but the catalog page/revision of nixpkgs will change. This prints the message:
ℹ️ No packages need to be upgraded in environment 'name'.
but then the lockfile is modified, which could be confusing.
We could either:
Not write the changes to the lockfile. That discards the information that there isn't an upgrade at some point in time, which isn't meaningless. I'm not sure if it's valuable.
Print the message (needs rewording):
ℹ️ No packages need to be upgraded in environment 'main'. A record of checking for an 'upgrade' was written to the lockfile.
The text was updated successfully, but these errors were encountered:
It sounds like we don't tell the user that "the catalog page/revision of nixpkgs will change" at all and if so, I'd agree that probably is not something we need to be user-facing right now.
In some cases, a
flox upgrade
will preserve derivations of all packages, but the catalog page/revision of nixpkgs will change. This prints the message:but then the lockfile is modified, which could be confusing.
We could either:
The text was updated successfully, but these errors were encountered: