Hey, thanks for your observations.
whk via <[email protected]> writes: > I believe this is user error rather than a 1.5.0rc1 error but I don't > see what I did wrong. I can provide details for each step if they are > relevant and wipe are retry if there is something I should do differently. > > Errors: > > * On generated system > o guix pull > > Updating channel 'guix' from Git repository at > 'https://git.guix.gnu.org/guix.git'... > guix pull: error: Git error: failed to connect to > git.guix.gnu.org: Operation timed out Codeberg has been struggling in the last few days, so to me it looks like you just hit the case when it did struggle. Just try it again. In case it persists further, report back. Or did you already do it multiple times? It's not really clear from your message. You can also try `wget https://codeberg.org` and `wget https://git.guix.gnu.org` to see if something is wrong with network. > > * guix pull --list-generations > > guix pull: error: profile > '/var/guix/profiles/per-user/root/current-guix' does not exist That is correct, until you pull successfully, there is no profile made by neither the installer nor guix system init. This could be changed in the future, to make it more convenient to users so that they do not have to `guix pull` initially to reconfigure, but I would think this would be the installer doing it, not guix system init. > > Scenario: > > * Created a fresh debian 12 vps instance > * Installed guix using the guix-install script > o > GUIX_BINARY_FILE_NAME=/root/guix/guix-binary-1.5.0rc1.x86_64-linux.tar.xz > /root/guix/guix-install.sh > o Installer required newgidmap which was not installed. Installed > with apt install rootlesskit > o guix --version verified 1.5.0rc1 was installed > * Created two partitions for a guix system install > * Installed guix onto partitions > o guix system init guix-minimal-config.scm /mnt/guix > o where guix-minimal-config.scm was... > > * Rebooted into the guix install and tried to do guix pull which > failed as above > > Unexpected: > > * guix --version on generated system returns 1.4.0-47.21ce6b3 rather > than the 1.5.0rc1 that was used to generate it This is expected in the way you created the system. When the 1.5.0 binary tarball comes out, the guix package its going to point to is the one that was bumped previously. So when you do guix system init with a configuration with %base-services, you will end up with an older guix. (`guix show guix` is the one you end up with) You could change the guix in guix-service-type to (current-guix) in case you wanted to end up with the same guix as you're using. See this as an example https://codeberg.org/guix/guix/src/branch/master/gnu/system/examples/vm-image.tmpl#L136. This is solved in the Guix System installer by bumping the guix package and making the system from commit that bumped it to 1.5.0rc1 rather than from commit tagged as 1.5.0rc1 directly. But on foreign distros, you're right it will end up like this. It's always better to first pull. This was the same case with 1.4.0. Maybe we could try doing something about it if it's unexpected for users, but I don't know what. The only possibility that comes to my mind to solve this would be to solve it similarly to the Guix System installer. We would distribute the binary tarballs with guix package from commit that has the package bumped. That would mean the tarballs aren't made from the tagged release commit itself, though. However, that would mean that `guix --version` would tell you it's something like `1.5.0rc1-1.<part of hash>` and that seems unexpected to me. I think that most users won't encounter this, though. That is because either they use Guix on a foreign distro and they did pull previously or they use the installer where it's solved. Thank you, Rutherther > > > Cheers, > W
