Skip to content

Silent schema upgrades are a tad unfriendly #1251

Description

@copumpkin

I was testing something (my changes to Nix for #1245) so I cloned master on a remote box I was working on, ran make install, and then ran inst/bin/nix-somehing. I worked on Nix for a while and then switched back to the host, and then all of a sudden all of my Nix commands failed immediately saying error: current Nix store schema is version 10, but I only support 7.

I don't particularly want to upgrade everything in this system to nixUnstable (and even if I did, it'd be kinda painful given that nothing works now). My current plan is to tinker with --dump-db (from nixUnstable) and --load-db (on an older one) and cross my fingers.

I think it'd be nice for some sort of configuration option saying "don't quietly upgrade my store", perhaps on by default. Then a simple nix-upgrade-store command would apply the logic when I ask for it, and all other commands would tell me that they need me to upgrade and that since it's a PITA to reverse, they won't do it for me.

Metadata

Metadata

Assignees

Labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions