<amf>
i have to, brand new hardware, that worked, when do i change the stateVersion in conf.nix?
2019-10-06
<{^_^}>
Special commands: find tell locate expand - Commands sorted by use count, page 0 (use ,<n> to view page <n>): tofu help libraries unstable escape'' library unfree declarative howoldis ping escape" callpackage paste overlay -a ask pinning profiling pr which-channel nixlang++ imperative xy cache fancy-uninstall xml exec pills wololo botsnack invite channels haskell loot stateversion home-manager stuck pointers escape-special tias timer dontask ifd nur
2019-09-30
<infinisil>
gyroninja: nixops stores stateVersion in the deployment state, which then gets included for the build, so you shouldn't need it
2019-09-28
<hpfr[m]>
So if i have affected services installed, how do i prepare them for changing the stateversion
<tilpner>
But some services change behaviour depending on stateVersion
<tilpner>
Not that much depends on stateVersion, if you're just running a desktop system, you might be just fine bumping it
2019-09-20
<{^_^}>
Special commands: find tell locate expand - Commands sorted by use count, page 0 (use ,<n> to view page <n>): tofu help libraries unstable escape'' library unfree declarative howoldis ping callpackage escape" overlay ask paste pinning -a profiling pr imperative nixlang++ which-channel cache xy exec wololo fancy-uninstall xml botsnack invite pills channels haskell loot stateversion home-manager stuck pointers escape-special tias timer dontask nur
2019-09-19
<arcnmx>
worldofpeace: the problem is basically the test spawns containers with a different stateVersion than its own so it's missing some x packages the containers need, then fails to get them from the cache?
<{^_^}>
[nixpkgs] @worldofpeace opened pull request #68363 → nixos/xterm: stateVersion disable by default → https://git.io/Jeq2c
2019-09-06
<worldofpeace>
srhb: right, and in the end it would be no-op for users like you who rely on it. We could use stateVersion, but I think it's kinda silly. And a warning if no DE or WM might be annoying.
2019-08-25
<{^_^}>
Special commands: find tell locate expand - Commands sorted by use count, page 0 (use ,<n> to view page <n>): tofu help libraries unstable unfree escape'' library declarative ping escape" overlay howoldis pinning -a ask callpackage profiling pr paste imperative cache which-channel xy wololo exec fancy-uninstall nixlang++ pills xml haskell loot stateversion botsnack channels home-manager stuck pointers tias timer dontask pure-eval runtimedeps thesis
2019-08-19
<{^_^}>
[nixpkgs] @matthewbauer closed pull request #66982 → nixos/timesyncd: run migration even if stateVersion is unset → https://git.io/fjFQr
<{^_^}>
[nixpkgs] @matthewbauer opened pull request #66982 → nixos/timesyncd: run migration even if stateVersion is unset → https://git.io/fjFQr
2019-08-16
<{^_^}>
Special commands: find tell locate expand - Commands sorted by use count, page 0 (use ,<n> to view page <n>): tofu help libraries unstable unfree library declarative escape'' ping overlay escape" pinning howoldis profiling -a ask pr callpackage imperative cache which-channel paste xy exec nixlang++ wololo fancy-uninstall pills stateversion xml botsnack channels haskell home-manager loot stuck pointers tias timer dontask pure-eval runtimedeps cloak
2019-08-15
<drakonis_>
matthewbauer, its breaking because your stateversion is unset
<infinisil>
Well you're supposed to have stateVersion set to the *initial* NixOS version you installed on the system
<infinisil>
Apparently you removed stateVersion at some point :)
2019-08-10
<{^_^}>
Special commands: find tell locate expand - Commands sorted by use count, page 0 (use ,<n> to view page <n>): tofu help libraries unstable unfree library declarative escape'' ping overlay escape" howoldis pinning profiling ask pr -a callpackage cache imperative which-channel paste xy exec nixlang++ wololo fancy-uninstall pills stateversion botsnack channels haskell home-manager loot stuck tias timer dontask pointers pure-eval runtimedeps xml cloak
2019-07-24
<adamt>
elvishjerricco: The postgres module choses a specific postgres pkg based on stateVersion. Having to look in the file system to figure it out would be impure, unless you could live with sticking all possible versions in the store, and just pick one on startup :P
<elvishjerricco>
I always though `stateVersion` was kind of bad form. Anything that needs state that may need to migrate should probably manage its own state variable with a file on the system, rather than with this setting that users often mess up
<adamt>
nixnothing: If you want to know what actually uses it, you can just grep for "stateVersion" in the nixpkgs repository.
<samueldr>
though yeah, it's *mostly* databases, but at a moment's notice anything stateful could end up being affected by stateVersion
<{^_^}>
Setting stateVersion to the latest release doesn't upgrade anything and can only break your setup at best. To actually upgrade NixOS see https://nixos.org/nixos/manual/#sec-upgrading. If you want to update the stateVersion option regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually migrated with the new value.
<aristid>
FYI, I want to change stateVersion: #65314
2019-06-26
<lordcirth_>
So I dug through the code a bit, and it seems that nixops does not set stateVersion, but records it based on how the machine first came up.
<{^_^}>
Setting stateVersion to the latest release doesn't upgrade anything and can only break your setup at best. To actually upgrade NixOS see https://nixos.org/nixos/manual/#sec-upgrading. If you want to update the stateVersion option regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually migrated with the new value.
<samueldr>
,stateVersion
<monokrome>
EG, to upgrade to 19.09 you move your channel up but leave stateVersion at 19.03 on a regular non nixops install
2019-06-20
<infinisil>
chrisq2: Nah stateVersion doesn't have anything to do with that (the name is confusing)
<chrisq2>
And that 16.?? stateVersion was set on the remote machine.
<chrisq2>
infinisil: Honestly have no idea, I tried to check the version but that fails with the error too. But it's odd as it's freshly installed a day ago? The only thing I thing might have been the cause is the `stateVersion` being set to an old 16.?? version.
2019-06-16
<{^_^}>
Special commands: find tell locate - Commands sorted by use count, page 0 (use ,<n> to view page <n>): tofu help libraries unstable unfree library escape'' declarative escape" overlay pr profiling ping ask pinning howoldis imperative which-channel -a xy wololo callpackage exec fancy-uninstall nixlang++ pills cache channels haskell home-manager ifd loot paste stateversion stuck tias timer runtimedeps cloak dontask error nur upgrade botsnack jdwhat
<{^_^}>
Special commands: find tell locate - Commands sorted by use count, page 0 (use ,<n> to view page <n>): tofu help libraries unstable unfree library escape'' declarative escape" overlay pr profiling ping ask pinning howoldis imperative which-channel -a xy wololo callpackage exec fancy-uninstall nixlang++ pills cache channels haskell home-manager ifd loot paste stateversion stuck tias timer runtimedeps cloak dontask error nur upgrade botsnack jdwhat
2019-06-11
<fschulze>
I just noticed stateVersion at the end is still 18.03
2019-06-02
<{^_^}>
Special commands: find tell locate - Commands sorted by use count, page 0 (use ,<n> to view page <n>): tofu help libraries unstable unfree library escape'' declarative escape" pr overlay ping profiling ask howoldis pinning imperative which-channel xy wololo exec fancy-uninstall nixlang++ pills -a cache callpackage channels haskell home-manager loot smart-questions stateversion stuck ifd tias paste runtimedeps timer cloak dontask error flakes nur
<immae>
jlv_: stateVersion changes the "state" version of the system, which is distinct from the systemVersion
<jlv_>
Wait, why doesn't changing stateVersion change the version?
<infinisil>
They set stateVersion to 19.03, but it turned out they were still on 18.03 xD
<infinisil>
I just recently encountered a user who changed stateVersion because they thought it would upgrade their system..
<{^_^}>
immae: Setting stateVersion to the latest release doesn't upgrade anything and can only break your setup at best. To actually upgrade NixOS see https://nixos.org/nixos/manual/#sec-upgrading. If you want to update the stateVersion option regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually migrated with the new value.
<infinisil>
,stateVersion immae
2019-05-11
<{^_^}>
Setting stateVersion to the latest release doesn't upgrade anything and can only break your setup at best. To actually upgrade NixOS see https://nixos.org/nixos/manual/#sec-upgrading. If you want to update the stateVersion option regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually migrated with the new value.
<jasongrossman>
,stateversion
2019-05-09
<infinisil>
I wouldn't mind using stateVersion more to have better defaults
<infinisil>
(which is the result of the docs when conditioning the default on stateVersion)
<infinisil>
samueldr: People aren't supposed to change stateVersion, so their existing set up will still work
<gchristensen>
I think, typically, each use of stateVersion gets a release note
2019-05-03
<{^_^}>
Special commands: find tell locate - Commands sorted by use count, page 0 (use ,<n> to view page <n>): tofu help libraries paste unfree unstable library escape'' declarative escape" overlay pr profiling howoldis ping pinning xy ask imperative which-channel wololo exec fancy-uninstall nixlang++ pills cache channels home-manager callpackage configsearch haskell loot stuck tias -a smart-questions stateversion timer cloak dontask error nur runtimedeps
2019-04-24
<gchristensen>
,stateVersion
<{^_^}>
Setting stateVersion to the latest release doesn't upgrade anything and can only break your setup at best. To actually upgrade NixOS see https://nixos.org/nixos/manual/#sec-upgrading. If you want to update the stateVersion option regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually migrated with the new value.
2019-04-19
<{^_^}>
drager1: Setting stateVersion to the latest release doesn't upgrade anything and can only break your setup at best. To actually upgrade NixOS see https://nixos.org/nixos/manual/#sec-upgrading. If you want to update the stateVersion option regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually migrated with the new value.
<infinisil>
,stateVersion drager1
2019-04-18
<jomik>
Guess I was looking for a "You should not set stateVersion to 19.03" ... Lol
<jomik>
Hmm, reading on `stateVersion` in release notes, it does not mention at any time that we sohuld change it to 19.03?
<{^_^}>
[nixpkgs] @worldofpeace opened pull request #58596 → nixos/rename: drop system.nixos.{stateVersion, defaultChannel} → https://git.io/fjkEs
2019-03-27
<jasongrossman>
infinisil: I knew I was going to have to expand what I said! I meant for many users, not for power users / developers. And even so maybe I was wrong, but I was close enough to right to explain my annoyance with stateVersion.
<jasongrossman>
samueldr: My problem with stateVersion is the amount of confusion it generates, in what's otherwise such an elegant and unconfusing system (once you grok it).
<samueldr>
jasongrossman: (I was kinda being silly here) is there anything specific with stateVersion, other than the name being unwholesome, that warranted the outburst?
<jasongrossman>
samueldr: I hate stateVersion so much I'm thinking of switching to Windows. Or OS/360.
<samueldr>
aw, checked something, I had hope stateVersion would still be unused in 19.03, but two packages will rely in it being pre or post 19.03 (syncthing and redmine)
<jasongrossman>
adamt: My understanding is that very little uses stateVersion.
<jasongrossman>
adamt: I doubt it, because it would be a lot of work for someone to work out the upgrade paths for all the old stateVersions.
<tilpner>
Huh, the ISO uses 18.03 as stateVersion
<jasongrossman>
avn: Changing stateVersion doesn't actually upgrade anything. I know it sounds like it does, but it's just a bad name.
<tilpner>
,stateVersion avn
<{^_^}>
avn: Setting stateVersion to the latest release doesn't upgrade anything and can only break your setup at best. To actually upgrade NixOS see https://nixos.org/nixos/manual/#sec-upgrading. If you want to update the stateVersion option regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually migrated with the new value.
<avn>
Folks, I have funny question -- how safe is to bump stateVersion to something better than 15.09? ;)
2019-02-20
<{^_^}>
Special commands: find tell locate - Commands sorted by use count, page 0 (use ,<n> to view page <n>): tofu library IFD unfree -A escape'' libraries declarative paste help callPackage stateVersion unstable pr profiling escape" overlay which-channel xy imperative exec howoldis NUR fancy-uninstall jDwhat nixlang++ ping channels loot pills wololo xml configsearch nixGL pinning runtimeDeps stuck timer cloak dontask error smart-questions tias upgrade
<{^_^}>
Special commands: find tell locate - Commands sorted by use count, page 0 (use ,<n> to view page <n>): tofu library IFD unfree escape'' -A libraries declarative paste help unstable callPackage stateVersion pr profiling escape" overlay which-channel imperative xy exec NUR fancy-uninstall howoldis ping channels loot nixlang++ pills xml configsearch jDwhat pinning runtimeDeps stuck timer cloak error nixGL smart-questions tias upgrade wololo dontask
2019-02-17
<samueldr>
because, if you did, it's not going to do anything, since stateVersion is NOT used to "statefully define the nixos version"
<lejonet>
samueldr: no, I've had that stateVersion for a while
<{^_^}>
lejonet: Setting stateVersion to the latest release doesn't upgrade anything and can only break your setup at best. To actually upgrade NixOS see https://nixos.org/nixos/manual/#sec-upgrading. If you want to update the stateVersion option regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually migrated with the new value.
<samueldr>
,stateVersion lejonet
<samueldr>
sorry if this is condescending, but did you *change* stateVersion?
<lejonet>
exist." when trying to deploy with nixops? The local system is running stateVersion 18.09, so it should be visible
<iqubic>
Changing the stateVersion might actually screw up your system really badly.
<iqubic>
stateVersion should be kept the same always. It's used for managing things like databases behind the scenes. DO NOT CHANGE IT.
<laalf>
hello! information about system.stateVersion is rather different around the web. if i dont change the stateversion, i wont get newer channels packages, right? there is no "nixos-stable" channel, right?
2019-02-10
<{^_^}>
Special commands: find tell locate - Commands sorted by use count, page 0 (use ,<n> to view page <n>): tofu IFD library unfree -A declarative escape'' paste libraries help stateVersion callPackage profiling pr unstable imperative which-channel escape" exec fancy-uninstall overlay xy NUR channels loot nixlang++ ping howoldis jDwhat pills pinning xml cloak error gctest.html nixGL runtimeDeps smart-questions tias upgrade wololo configsearch haskell
2019-02-07
<{^_^}>
Special commands: find tell locate - Commands sorted by use count, page 0 (use ,<n> to view page <n>): tofu IFD library unfree declarative escape'' -A paste libraries stateVersion help dnw profiling pr callPackage imperative unstable escape" which-channel exec fancy-uninstall overlay xy NUR channels home-manager loot nixlang++ ping howoldis jDwhat pills pinning xml cloak error gctest.html nixGL smart-questions tias upgrade wololo configsearch
2019-02-06
<srhb>
Well, aside from a few kill switches that prevent you from doing Known Bad Stuff (stateVersion)
2019-02-02
<{^_^}>
Special commands: find tell locate - Commands sorted by use count, page 0 (use ,<n> to view page <n>): tofu IFD library unfree declarative escape'' -A stateVersion help libraries dnw pr profiling paste imperative callPackage escape" which-channel exec fancy-uninstall channels home-manager loot nixlang++ overlay ping unstable xy NUR jDwhat pills pinning cloak error gctest.html howoldis nixGL smart-questions tias upgrade wololo configsearch haskell
2019-01-25
<{^_^}>
Special commands: find tell locate - Commands sorted by use count, page 0 (use ,<n> to view page <n>): tofu IFD library declarative unfree -A escape'' stateVersion dnw help pr profiling paste escape" imperative libraries callPackage fancy-uninstall exec loot overlay xy home-manager jDwhat nixlang++ pills pinning channels cloak error gctest.html nixGL ping tias unstable upgrade which-channel NUR haskell smart-questions timer wololo bootfull
2019-01-19
<pbb>
okay, so it will actually install a stable system, even though it generates a config file with stateVersion 19.03
<pbb>
At least I think I understand the concept of stateVersion, but it's still confusing that after downgrading my installation tools to 18.09 they still generate new configuration files with stateVersion=19.03
<simpson>
pbb: Hm. I guess that that doesn't directly address your concern. `stateVersion` is a version for any stateful data on your system which might be versioned in a way that you don't want to have changed suddenly without your knowledge.
<{^_^}>
Setting stateVersion to the latest release doesn't upgrade anything and can only break your setup at best. To actually upgrade NixOS see https://nixos.org/nixos/manual/#sec-upgrading. If you want to update the stateVersion option regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually migrated with the new value.
<simpson>
,stateVersion
<jasongrossman>
pbb: "stateVersion" is a very misleading name.
<pbb>
ey, now I definitely changed the channel to 18.09 before I installed the install tools and it still generates configurations.nix with stateVersion 19.03!
2019-01-15
<jasongrossman>
samueldr: IIRC you had a really good idea about what to rename stateVersion to.
<{^_^}>
jasongrossman: Did you mean stateVersion?
<{^_^}>
Setting stateVersion to the latest release doesn't upgrade anything and can only break your setup at best. To actually upgrade NixOS see https://nixos.org/nixos/manual/#sec-upgrading. If you want to update the stateVersion option regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually migrated with the new value.
<jasongrossman>
,stateversion
<simpson>
kini: If you don't see anything interesting to you in the release notes, then don't change `stateVersion`. That's it.
<clever>
Celmor: and you shouldnt try to change stateVersion to upgrade it
2019-01-08
<theo_>
samueldr: I had changed stateVersion over a month ago, it was only this recent channel upgrade that broke things
<{^_^}>
stateVersion redefined, was defined as: Setting stateVersion to the latest release doesn't update anything and can only break your setup at best. If you want to regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually upgraded with the new value
<infinisil>
,stateVersion = Setting stateVersion to the latest release doesn't upgrade anything and can only break your setup at best. To actually upgrade NixOS see https://nixos.org/nixos/manual/#sec-upgrading. If you want to update the stateVersion option regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually migrated with the new value.
<samueldr>
theo_: by changing stateVersion? highly unlikely, nothing checks against 18.09 in nixpkgs
<samueldr>
though changing it to 18.09 is a no-op since nothing changed between 18.03 and 18.09 and was using stateVersion
<{^_^}>
theo_: Setting stateVersion to the latest release doesn't update anything and can only break your setup at best. If you want to regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually upgraded with the new value
<samueldr>
,stateVersion theo_
2019-01-03
<{^_^}>
fusion809: Setting stateVersion to the latest release doesn't update anything and can only break your setup at best. If you want to regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually upgraded with the new value
<ottidmes>
,stateVersion fusion809
2018-12-25
<Orbstheorem>
{^_^}: Thanks for the note about stateVersion (sorry, I got disconnected yesterdays ^^)
2018-12-24
<{^_^}>
Orbstheorem: Setting stateVersion to the latest release doesn't update anything and can only break your setup at best. If you want to regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually upgraded with the new value
<ottidmes>
,stateVersion Orbstheorem
2018-12-13
<kvda>
A bump of stateVersion is a suggestive indicator that you might have to do manual checks, and invalidates the revisions too?
<kvda>
"The idea is: a bump of stateVersion potentially can’t be reverted, and potentially needs manual intervention (eg. with pgsql upgrades)."
2018-12-11
<simpson>
,stateVersion
<{^_^}>
Setting stateVersion to the latest release doesn't update anything and can only break your setup at best. If you want to regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually upgraded with the new value
<Growpotkin>
what does "stateVersion" actually do? I have never come to understand that
<simpson>
What gchristensen said. As a sysadmin, I really do want to set stateVersion *once*, at install, and hopefully never again.
<gchristensen>
the best bet is to forget stateVersion exists until release notes say it should change
<simpson>
nixos-rebuild will not change stateVersion nor anything else in your configuration.nix.
<rsully>
does nixos-rebuild update stateVersion? or is it still a manual process?
<rsully>
aah ok "stateVersion has nothing to do with the current version of the system"
<simpson>
rsully: To add onto that: The purpose of stateVersion is to be set *once*, when you install. You can change it after reading release notes. The entire goal is to enable most folks to cleanly upgrade between releases without worrying about having to upgrade Pg tables or other stateful data.
<{^_^}>
rsully: Setting stateVersion to the latest release doesn't update anything and can only break your setup at best. If you want to regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually upgraded with the new value
<samueldr>
,stateVersion rsully
<rsully>
is stateVersion to track a nix release, or does that property not really do anything? sorry I have not poked around much, very overwhelming
2018-12-06
<goibhniu>
AFAIK stateVersion is only used for a few system services, which you may not even be using, e.g. postgres
<symphorien>
don't change stateVersion
<{^_^}>
Setting stateVersion to the latest release doesn't update anything and can only break your setup at best. If you want to regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually upgraded with the new value
<symphorien>
,stateVersion
2018-12-03
<Myrl-saki>
oldandwise: Do not change the stateVersion.
2018-12-02
<{^_^}>
simukis: Setting stateVersion to the latest release doesn't update anything and can only break your setup at best. If you want to regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually upgraded with the new value
<samueldr>
,stateVersion simukis
<{^_^}>
growpotkin: Setting stateVersion to the latest release doesn't update anything and can only break your setup at best. If you want to regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually upgraded with the new value
<samueldr>
,stateVersion growpotkin
<samueldr>
did you touch stateVersion?
2018-11-22
<{^_^}>
Special commands: find locate tell - Commands sorted by use count, page 0 (use ,<n> to view page <n>): library tofu profiling -A dnw escape'' unfree pr escape" imperative pills unstable ask callPackage error ping pinning stateVersion allah channels declarative dentalplan exec nixlang++ overlay upgrade wololo IFD NUR cloudfront escape-special haskell help info logs loot nixeval paste runtimeDeps stuck tias timer whomademe wrapper arm bootfull context
2018-11-21
<{^_^}>
Special commands: find locate tell - Commands sorted by use count, page 0 (use ,<n> to view page <n>): library tofu profiling -A dnw escape'' unfree pr escape" imperative pills unstable ask error ping pinning stateVersion allah callPackage declarative dentalplan exec nixlang++ overlay upgrade wololo IFD NUR channels cloudfront escape-special haskell help info logs loot paste runtimeDeps stuck tias timer whomademe wrapper arm bootfull context
<{^_^}>
Special commands: find locate tell - Commands sorted by use count, page 0 (use ,<n> to view page <n>): library tofu profiling -A dnw escape'' unfree pr escape" imperative pills unstable ask error ping pinning stateVersion allah callPackage declarative dentalplan nixlang++ overlay upgrade wololo IFD NUR channels cloudfront escape-special exec haskell help info logs loot paste runtimeDeps stuck tias timer whomademe wrapper arm bootfull context
2018-11-16
<{^_^}>
andrewrk: Setting stateVersion to the latest release doesn't update anything and can only break your setup at best. If you want to regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually upgraded with the new value
<infinisil>
,stateVersion andrewrk
2018-11-12
<clever>
Zer000: did you change the stateVersion? (or is it missing)
2018-11-10
<{^_^}>
[nixpkgs] @samueldr opened pull request #50112 → Renames stateVersion to stateEpoch → https://git.io/fpL57
2018-11-02
<{^_^}>
Special commands: find locate tell - Commands sorted by use count, page 0 (use ,<n> to view page <n>): library tofu dnw pr -A imperative pills profiling escape'' paste ping pinning unfree unstable ask declarative error escape" help overlay stateVersion upgrade IFD NUR allah callPackage cloudfront dentalplan escape-special exec info loot nixlang++ runtimeDeps tias timer whomademe wololo wrapper arm bootfull channels context fancy-uninstall github
2018-10-31
<{^_^}>
Special commands: find locate tell - Commands sorted by use count, page 0 (use ,<n> to view page <n>): library tofu dnw pr -A imperative pills profiling ping pinning unfree unstable ask declarative error escape'' overlay paste stateVersion upgrade IFD NUR allah callPackage cloudfront dentalplan escape" exec help info loot nixlang++ runtimeDeps tias timer whomademe wololo wrapper arm bootfull channels context escape-special fancy-uninstall github
2018-10-21
<samueldr>
and if you want to update, the safest way is to look at everything using `stateVersion` in <nixos/modules>
<samueldr>
but the main thing to remember is that as of today, it's not an issue to keep older stateVersion
<samueldr>
I'm pretty sure most stateVersion using options are folder locations
<samueldr>
pie___: no warnings, and as of right now, and nothing in the close future, is expected to break at any older stateVersion (AFAIK)
<pie___>
so, afaict stateversion is basically for not breaking things on an update that generally would?
<{^_^}>
Setting stateVersion to the latest release doesn't update anything and can only break your setup at best. If you want to regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually upgraded with the new value
<samueldr>
,stateVersion
<samueldr>
stateVersion shouldn't be touched, unless someone knowledgeable explains why you would
2018-10-18
<makefu>
sir_guy_carleton: you probably should not change stateVersion unless you do not care about migration issues
2018-10-12
<Zajcev_>
ok I see, nad how is it related with containers? should I declare stateversion in every container?
2018-10-08
<jD91mZM2>
Speaking of stateVersion... I should leave that unchanged right? Even if it's 18.03 and I'm on 18.09?
2018-10-07
<{^_^}>
Special commands: find locate tell - Commands sorted by use count, page 0 (use ,<n> to view page <n>): library dnw pr tofu unstable -A ask ping pinning IFD NUR allah cloudfront info nixcon overlay paste profiling stateVersion unfree whomademe wololo arm bootfull callPackage channels context declarative dentalplan error escape" escape'' escape-special exec fancy-uninstall github hardware haskell help home-manager howoldis imperative logs loot nix-env-r
<samueldr>
though it may need to start at 20, so it could reuse the stateVersion numbers wholesale
<samueldr>
the stateVersion gives the fuzzy feeling of knowing that it relates to a nixos release
<clever>
Ashy: stateVersion did recently get moved, but that broke nixops and a few other things
<clever>
Ashy: stateVersion has no impact on what channel your using, and changing it breaks the very thing its meant to fix
<Acou_Bass>
so stateVersion is more for the database schema than the OS itself?
<Acou_Bass>
i dont actually have stateVersion set in my configuration.nix at all
<samueldr>
the big tldr is that stateVersion is the "first installed version"
<zduch4c>
so the stateVersion will stay the same?
<{^_^}>
Setting stateVersion to the latest release doesn't update anything and can only break your setup at best. If you want to regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually upgraded with the new value
<samueldr>
,stateVersion
2018-09-30
<rawtaz>
MrAngel: if you installed it just today, perhaps it's better to use a more recent "infector" to get a newer stateVersion
<GiGa|Laptop>
stateVersion's only mentioned in relation to sshd. Won't be touching it
<{^_^}>
Setting stateVersion to the latest release doesn't update anything and can only break your setup at best. If you want to regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually upgraded with the new value
<infinisil>
,stateVersion
2018-09-12
<clever>
stphrolland: stateVersion must not be changed
2018-09-11
<clever>
and the dataDir is either /var/lib/mysql or /var/mysql, depending on your stateVersion
<samueldr>
postgresql.package isn't set using stateVersion?
<samueldr>
hmm, may change despite stateVersion? (haven't verified anything)
<srhb>
I'm fine with breakage on stateVersion changes.
<srhb>
I see, the dataDir is in fact dependent on the package version which may change despite stateVersion.
<samueldr>
(turns out everything was still in the stateful dir and put the stateVersion and everything was back)
<samueldr>
from 17.03 -> 17.09 I had a container without stateVersion and "lost" all data
<samueldr>
i should add "4. you have the time to fix unintended consequences of changing stateVersion"
<{^_^}>
Setting stateVersion to the latest release doesn't update anything and can only break your setup at best. If you want to regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually upgraded with the new value
<samueldr>
,stateVersion
<samueldr>
IIRC there was an update (or proposed update) to the stateVersion comment
<LnL>
samueldr: yeah the main problem is how do we avoid forgetting about the deprecation, there is .version which could be used similar to stateVersion but for warnings
<samueldr>
if you're using something at stateVersion 17.09, that "thing" using the deprecated version could still make use of it
<sphalerite>
since stateVersion shouldn't change
<LnL>
using something similar to stateVersion would make sense I think
<sphalerite>
d1rewolf: as long as you have stateVersion set correctly (no later than 18.03 at this point in time I believe) it shouldn't break anything majorly I think
2018-08-09
<clever>
that is also the simplest way to change the stateVersion, at the cost of data loss
<fresheyeball>
the machine I am building with is stateVersion 17.03 but OS version 18.03
<clever>
elvishjerricco: changing the stateVersion back restored the old datadir, and the whole db
<elvishjerricco>
Does nixops handle stateVersion for you?
<clever>
elvishjerricco: i also recently got surprised by a recent accidental change of stateVersion, the datadir for postgres now contains the version#
<elvishjerricco>
but stateVersion == 17.09 means pg.superUser = root
<elvishjerricco>
i.e. the pg db will have a root role, but not a postgres role, and having stateVersion == 18.03 will set pg.superUser == postgres
<elvishjerricco>
fresheyeball: Yea, but if your pg db was created with stateVersion == 17.09, and you've since changed it to 18.03, it'll be inconsistent
<samueldr>
so if you changed stateVersion (which you probably should never do) you may have issues
<samueldr>
do note that the stateVersion (iirc) 17.09→18.03 changed the default superUser
<srk>
you like have one option defined in two places (hope it's not stateVersion)
<sophiag>
sorry, phone call. so i'm bricked because i tried to change the stateVersion to see if it could prevent me from running 16.09 for all eternity :/
<sophiag>
changing the stateVersion back doesn't seem to have helped
<clever>
sophiag: stateVersion cant corrupt the nix store
<sophiag>
but google is telling me it could be due to bumping my stateVersion to see if it would help with that (i know you're not suppose to do that, but theoretically rollbacks should work as well)
<noqqe>
tilpner: k, so it would make sense for me to figure out what version I initially installed and set this as a stateVersion ?
<tilpner>
So... you're not supposed to ever change stateVersion
<sophiag>
my guess is it will crash if i rebuild switch without changing the stateVersion back
<sphalerite>
well you shouldn't really bump the stateVersion at all
<sophiag>
modulo having bumped the stateVersion...
<sophiag>
oh, i bumped the stateVersion
<LnL>
yeah, we could drop it with stateVersion 18.09 or later
<sophiag>
well, my stateVersion is 18.03 and i'm definitely not changing that again
<sophiag>
ah. that's good to know. what prompted me to change stateVersion was seeing that i was still on 1.11.6
<sophiag>
so, i think my entire issue should have been patched at 17.09 and i just never got it because i had my stateVersion pinned to 16.09. now after upgrading i'm in tty hell and somehow missing the symlink to my channels...
<sophiag>
or it's possible bumping my stateVersion fixed that and now i'm left with this problem
<{^_^}>
Setting stateVersion to the latest release doesn't update anything and can only break your setup at best. If you want to regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually upgraded with the new value
<samueldr>
,stateVersion
<samueldr>
updating stateVersion is always a "bit risky" (you need to at least take a look at some things)
<sophiag>
well, also because with stateVersion 16.09 Nix wouldn't upgrade beyond 1.11.6
<sophiag>
i just changed my stateVersion for the first time and upgraded on the slim chance it may fix a year+ old bug related to gpu switching and grub-install is reporting the error "/boot doesn't look like an EFI partition." fwiw, it had no problems with the i386 version. i feel like i've come across this before, but can't remember the fix
<LnL>
Twey: yeah, you shouldn't change the value of stateVersion unless you read the changelog first and migrate things you use first
<Mic92>
However since this usually requires manual intervention it is bound too stateVersion
<Mic92>
higher stateVersions will receive different postgresql versions for example.
<Mic92>
Twey: you can read the changelog to know what will change, if you upgrade stateVersion
2018-06-16
<tenten8401>
should stateVersion still be 18.09 or unstable?
2018-06-05
<infinisil>
See the link above what uses stateVersion, it's not only databeses
<{^_^}>
avn: Setting stateVersion to the latest release doesn't update anything and can only break your setup at best. If you want to regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually upgraded with the new value
<infinisil>
,stateVersion avn
<manveru>
avn: stateVersion should be the version you first installed
2018-06-04
<LnL>
!stateVersion
2018-06-01
<neonfuz>
I'm really just shooting in the dark here but I tried "nix-instantiate '<nixos>' --eval -A system" but that gives me the system string, not a set containing stateVersion
2018-05-31
<samueldr>
as part of the changes one would have to do when changing stateVersion (I know you shouldn't really), would it be a good idea (and possible) to also force a change in a [/nix/]/var/stateVersion file, which could be used by the module system to throw an error for those changing stateVersion hoping to update to the next release?
2018-05-28
<{^_^}>
All commands: -A areyoualive ask callPackage channels cloudfront error escape" escape'' help hint home-manager karma library magic nix-env-r nixeval notfound outPath paste pills ping pinning runtimeDeps rust stateVersion stuck tofu unfree unstable whomademe
2018-05-21
<sphalerite>
oooh we now have a warning for stateVersion not being set! That's good
2018-05-20
<{^_^}>
All commands: -A areyoualive ask callPackage channels cloudfront error escape" escape'' help hint home-manager karma library nix-env-r nixeval notfound outPath paste pills ping pinning runtimeDeps rust stateVersion stuck tofu unfree unstable whomademe
<{^_^}>
Setting stateVersion to the latest release doesn't update anything and can only break your setup at best. If you want to regardless, Ctrl-F for "stateVersion" in https://nixos.org/nixos/manual/release-notes.html to see things that need to be manually upgraded with the new value
<infinisil>
,stateVersion
<clever>
rauno: the stateversion is based on the image nixops first booted the machine with, and in general, it should only be changed when reinstalling, enless your prepared to deal with the migrations
2018-05-19
<infinisil>
In the second last commit in that history it just moves from options.system = { nixos.stateVersion to options.system.nixos = { stateVersion = ...
<clever>
infinisil: i dont see a nixos in the attrpath for stateVersion
2018-05-15
<{^_^}>
All commands: -A areyoualive ask callPackage channels cloudfront error escape" escape'' help hint home-manager karma library nix-env-r nixeval notfound outPath paste pills ping pinning runtimeDeps stateVersion stuck tofu unfree unstable
<{^_^}>
All commands: -A areyoualive ask callPackage channels cloudfront error escape" escape'' help hint home-manager karma library nix-env-r nixeval notfound outPath paste pills ping pinning runtimeDeps stateVersion stuck tofu unfree unstable
2018-05-14
<{^_^}>
[nixpkgs] @xeji pushed to master « nixos/tests: prevent stateVersion warnings in eval »: https://git.io/vpQMj
2018-05-13
<{^_^}>
[nixpkgs] @xeji pushed to master « nixos/tests: set default stateVersion in test VMs »: https://git.io/vp9wP
<{^_^}>
→ 095fe5b4 by @oxij: nixos: rename system.{stateVersion,defaultChannel} -> system.nixos.\1
<{^_^}>
All commands: -A areyoualive ask callPackage channels cloudfront escape" escape'' help library notfound paste pills ping stateVersion stuck tofu unfree
<{^_^}>
All commands: -A ask callPackage channels cloudfront escape" escape'' help library notfound pills stateVersion stuck tofu unfree
2018-04-24
<{^_^}>
[nixpkgs] @oxij opened pull request #39447 → nixos: warn on missing `stateVersion` → https://git.io/vpnJt
<clever>
robstr: does stateVersion exist anywhere in your config?
<clever>
so, it needs to know the version of the state, which is defined in the stateVersion
<clever>
robstr: you changed the stateVersion
2018-04-21
<samueldr>
though, it *can* be updated safely, but if you do, first read the release notes, then grep through <nixpkgs/nixos> for stateVersion on *anything* you are using
<samueldr>
what stateVersion means is "at which nixos version was the stateful stuff made", which is mostly used by databases and such
<samueldr>
ivanivan: you shouldn't change the stateVersion unless the docs indicate you should
<ivanivan>
The NixOS release notes mention a change to matrix-synapse defaults for stateVersion 18.03, but that's all they say.
2018-04-18
<iqubic>
make sure to reset stateVersion if you updated that.
<iqubic>
Leave the stateVersion as it is.
<symphorien>
Stateversion has nothing to do with the current version of the system
2018-04-14
<elvishjerricco>
joepie91: Agreed. Took me a while to take the time to lookup what stateVersion does. And by that point I'd already changed it :P
<monokrome>
Yeah, I have no intention of changing stateVersion
<disasm>
you can change stateVersion, but you have to read through ALL the release notes and find out all the things that were changed between states. For example, I changed my stateVersion between 17.03 and 17.09 I think it was because I wanted the different postgresql layout per version that was introduced. but other than things like that, you shouldn't touch it.